docs: record the misconceptions we corrected, remove superseded docs, and design concurrent author windows

docs/TODO.md

@@ -102,8 +102,7 @@ Their argument for each is in [gitops-api-open-asks.md](future/gitops-api-open-a
   watch it took over. Redis becomes required in this mode.
   [ha-gittarget-distribution-plan.md](future/ha-gittarget-distribution-plan.md).
 - [ ] Re-assess unifying the pending-write kinds
-  ([idea-unify-pending-write-kinds.md](future/idea-unify-pending-write-kinds.md), now four kinds,
-  not two). Deferred.
+  (grouped window, resync and request record, since #450 removed the atomic kind). Deferred.
 - [ ] Improve queue and worker observability, with more high-load tests.
 
 ## Watch plane
@@ -177,12 +176,10 @@ Their argument for each is in [gitops-api-open-asks.md](future/gitops-api-open-a
 ## Docs and vocabulary
 
 - [ ] **Stale design-doc headers**, one docs PR: [open-asks-priority.md](design/open-asks-priority.md)
-  (#339 closed, #23 fixed), [gittarget-api-wave.md](design/gittarget-api-wave.md) (riders shipped),
+  (#339 closed, #23 fixed),
   [git-write-preflight.md](design/git-write-preflight.md) (superseded by the red-status plan),
-  [commitrequest-save-wait-options.md](design/commitrequest-save-wait-options.md) (written against
-  `closeDelay`), [gittarget-red-status-plan.md](design/gittarget-red-status-plan.md) (steps 5 and 6
-  built), [watch-and-catalog-architecture.md](design/watch-and-catalog-architecture.md)
-  (superseded), [target-watch-plan.md](design/target-watch-plan.md) (queue depth is 1000, not 100),
+  [gittarget-red-status-plan.md](design/gittarget-red-status-plan.md) (steps 5 and 6
+  built), [target-watch-plan.md](design/target-watch-plan.md) (queue depth is 1000, not 100),
   and the go-git version in [azure-devops-multi-ack.md](design/azure-devops-multi-ack.md) and
   [gittarget-parent-empty-repository.md](design/gittarget-parent-empty-repository.md).
 - [ ] **Wrong claims in design bodies**: [support-contract.md](design/support-boundary/support-contract.md)

docs/architecture.md

@@ -1326,8 +1326,7 @@ peer of any named-namespace collection on the same type, never a replacement for
 
 Desired state comes from one **raw watch per `(GitTarget, GVR, scope)`**. Each event is sanitized, diffed
 against current Git content, and applied. There is no separate per-type object store to reconstruct,
-because Git already holds current state. This section is the authoritative contract; the
-[watch-first design record](finished/watch-first-ingestion-architecture.md) is historical context.
+because Git already holds current state. This section is the authoritative contract.
 
 - **Manager**: [internal/watch/manager.go](../internal/watch/manager.go)
 - **Watch / replay / sweep**: [internal/watch/target_watch.go](../internal/watch/target_watch.go)
@@ -2035,8 +2034,6 @@ Deeper dives live under [docs/design/](design/):
 
 **Ingestion, attribution, and reconcile:**
 
-- [Watch-first ingestion design record](finished/watch-first-ingestion-architecture.md): historical context
-  for the current watch-only object-state model and optional audit attribution.
 - [Attribution: how a commit gets its author](spec/attribution.md):
   the two halves, the tier ladder, and the wait.
 - [Attribution facts as a stream, not a keyspace](finished/attribution-fact-stream.md): the shipped
@@ -2054,7 +2051,6 @@ Deeper dives live under [docs/design/](design/):
 - [The support contract: what we edit, what we refuse, and why](design/support-boundary/support-contract.md)
 - [The applier claim](design/apply-trigger.md)
 - [Git credentials interop](finished/git-credentials-interop.md)
-- [SOPS/age key management](finished/sops-repo-bootstrap-and-key-management-architecture.md)
 - [Commit signing](commit-signing.md)
 - [Interpreting metrics](interpreting-metrics.md)
 

docs/components.md

@@ -270,9 +270,5 @@ Three gates can stop a type before it reaches a stream:
 
 - [`architecture.md`](architecture.md) for how the pieces work together, starting at Ground Rules
   and Mental Model.
-- [`design/watch-and-catalog-architecture.md`](design/watch-and-catalog-architecture.md) for the
-  target three-layer watch model: collections, the confidence model, and the managed projection.
 - [`design/target-watch-plan.md`](design/target-watch-plan.md) for the implementable plan that
   replaces wholesale stream replacement with an incremental diff.
-- [`design/data-plane-triggering.md`](design/data-plane-triggering.md) for why that refactor is
-  needed, starting from the production failure that prompted it.

docs/design/branch-worker-event-model.md

@@ -574,7 +574,7 @@ The detailed design records continue to own adjacent policy:
   project them. A sibling scope's success cannot clear another scope's refusal.
 - [Configuration freshness](gittarget-configuration-freshness.md): watch-plan application and
   publication are separate observations. This design does not require new public freshness fields.
-- [API boundaries](gittarget-api-wave.md) and
+- API boundaries and
   [push notifications](apply-trigger.md): a remote-change notification
   requests work through the owner. It does not become another checkout writer or prove that Git
   changes reached the source cluster.