simple-agent-manager · Sep 30, 2026 · Sep 30, 2026 · Sep 30, 2026 · Sep 30, 2026 · Sep 30, 2026
diff --git a/packages/cloud-init/tests/generate.test.ts b/packages/cloud-init/tests/generate.test.ts
@@ -557,7 +557,7 @@ describe('slice CPU shares', () => {
   // Memory already had a reservation for the vm-agent because starvation there
   // KILLS it. CPU had none, so a workspace saturating the box could delay the
   // heartbeat until the control plane declared the node dead — the failure mode
-  // recorded in tasks/backlog/2026-08-25-build-concurrency-backpressure.md.
+  // recorded in tasks/archive/2026-08-25-build-concurrency-backpressure.md.
   function sliceDirectives(path: string, overrides?: Partial<CloudInitVariables>): string {
     return getWriteFile(path, overrides).content;
   }

diff --git a/packages/shared/src/constants/scaling.ts b/packages/shared/src/constants/scaling.ts
@@ -66,7 +66,7 @@ export const MAX_WARM_NODE_TIMEOUT_MS = 4 * 60 * 60 * 1000; // 4 hours
  *   ceiling is the only backstop against real usage exceeding declared usage.
  * - Sustained CPU saturation is not purely a slowdown on this platform: it has
  *   previously starved the vm-agent heartbeat loop and produced false
- *   `node_not_live` task failures (`tasks/backlog/2026-08-25-build-concurrency-backpressure.md`).
+ *   `node_not_live` task failures (`tasks/archive/2026-08-25-build-concurrency-backpressure.md`).
  *   That incident's own mitigation — a per-node build queue — covers concurrent
  *   devcontainer builds but not steady-state contention between running
  *   workspaces, so admission keeps a real margin.

diff --git a/tasks/active/2026-09-03-projectdata-production-capacity-emergency.md b/tasks/active/2026-09-03-projectdata-production-capacity-emergency.md
@@ -606,3 +606,40 @@ Current live threads that will actually move this number (do not duplicate them
 
 Close this task when production `sql.databaseSize` is measured at or below 9 GB and the
 observation window in the acceptance criteria above has been recorded.
+
+## Reconciliation — 2026-09-30 (weekly queue audit)
+
+**Verdict: stays active.** The headline criterion is further from met than a week ago, and the
+drain that was supposed to move it has been stopped since 2026-09-27.
+
+Measured 2026-09-30 (read-only production D1):
+
+- `project_data_storage_telemetry` for `01KHRJGANBBWGDY1NZ0KVF0D4J`: **10,297,155,584 bytes**
+  (usage ratio 1.0297, status `degraded`) at 05:34Z. That is up from 10,103,668,736 at the
+  2026-09-23 audit and 10,124 MB on the morning of 2026-09-29.
+- `project_data_archive_circuit_breakers`: SAM's breaker is **`open`** with reason
+  `attempts_exhausted:CompactArchiveTimeoutError`, opened 2026-09-27 16:47:58Z and never closed.
+  The last SAM archive publish was 2026-09-27 14:08:35Z. Other projects had published 172
+  archives since the breaker opened (as of about 05:40Z), so the sweep itself is healthy.
+- SAM archive migrations: 322 `published`, 23 `frozen`, 3 `failed` (`156046f1`, `5ed87b67`,
+  `ff721a49`, all 2026-09-27) and 2 `poisoned` (`6d6f3099` since 2026-09-15, and `5f82299c`, the
+  one that opened the breaker).
+
+What changed since the last audit:
+
+- Slice B, exhaustive archive search: PR #2136, merged 2026-09-27.
+- Abandon-migration control in Admin → Storage: PR #2140, merged 2026-09-24.
+- Drain tripled (18-minute sweep cadence, 2.4M daily write budget): PR #2161, merged 2026-09-27
+  05:12Z. Its own 48-hour rollback trigger includes "the breaker opening"; the breaker opened
+  eleven hours later and the trigger was never acted on.
+- Slice C (bounded root history indexing): no PR yet. Its code already exists as commit
+  `7868bc894` ("fix(search): complete bounded root history indexing", 2026-09-22) on the unmerged
+  parent branch `sam/implement-reliable-projectdata-archiving-tc49jm`, the same branch Slices A and
+  B were carved from. The plan lives in idea `01M0YZNBKSKQZ47NC0K7M8N5AX`.
+
+Next actions, in order. These are human-gated production operations, not code:
+
+1. Decide on the #2161 rollback trigger (revert the interval to 3600000, or keep 18 minutes).
+2. Abandon or retry the failed/poisoned migrations first. Closing the breaker while `156046f1`,
+   `5ed87b67` and `ff721a49` are still failed risks re-poisoning it at once.
+3. Close SAM's breaker from Admin → Storage (phone-usable, PR #2135).
diff --git a/...26-02-15-user-configurable-mcp-servers.md → ...26-02-15-user-configurable-mcp-servers.md b/...26-02-15-user-configurable-mcp-servers.md → ...26-02-15-user-configurable-mcp-servers.md
@@ -317,3 +317,7 @@ If implementing hybrid approach, need clear precedence:
 - [ ] Configuration is persistent across workspace restarts
 - [ ] Clear documentation for adding custom MCP servers
 - [ ] (Optional) Visual UI for managing MCP servers without editing JSON
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as superseded (not built as written). Evidence: Shipped as BYO MCP servers (#1892, #2186; mcp_connections schema.ts:2069; SettingsMcpServers.tsx); survivor tasks/archive/2026-08-23-byo-mcp-servers.md; file already bannered "SUPERSEDED, do not execute"._
diff --git a/...og/2026-02-28-fix-flaky-vm-agent-tests.md → ...ve/2026-02-28-fix-flaky-vm-agent-tests.md b/...og/2026-02-28-fix-flaky-vm-agent-tests.md → ...ve/2026-02-28-fix-flaky-vm-agent-tests.md
@@ -67,3 +67,7 @@ A `time.Sleep(50*time.Millisecond)` before attaching the replay viewer. Simple b
 - [ ] No `time.Sleep` used as the fix (Options A or B preferred)
 - [ ] Other replay-related tests still pass
 - [ ] Run with `-race` flag to verify no data races
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as superseded (not built as written). Evidence: Survivor tasks/backlog/2026-07-04-fix-flaky-tests-at-root.md (item 3 says this file's root cause is wrong)._
diff --git a/...log/2026-02-28-mobile-chat-ux-overhaul.md → ...ive/2026-02-28-mobile-chat-ux-overhaul.md b/...log/2026-02-28-mobile-chat-ux-overhaul.md → ...ive/2026-02-28-mobile-chat-ux-overhaul.md
@@ -183,3 +183,7 @@ The project header row (project name, repo link, Status/Settings buttons) needs
 - [ ] Hamburger menu on the right side, matching drawer direction
 - [ ] Chat panel fills available vertical space without page-level scroll conflicts
 - [ ] All desktop layouts unaffected
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #220: AppShell mobile header, MobileSessionDrawer, full-bleed chat._
diff --git a/...nify-project-chat-through-do-streaming.md → ...nify-project-chat-through-do-streaming.md b/...nify-project-chat-through-do-streaming.md → ...nify-project-chat-through-do-streaming.md
@@ -75,3 +75,7 @@ Unify the project chat message flow through the DO as the single source of truth
 - [ ] `useProjectAgentSession` removed from project chat (kept for workspace chat)
 - [ ] No "Agent offline" banner in project chat
 - [ ] Message history fully preserved when switching between conversations
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as superseded (not built as written). Evidence: #978 / tasks/archive/2026-05-12-do-only-chat-typewriter.md: all chat through the DO with typewriter rendering._
diff --git a/...klog/2026-03-09-quick-chat-mode-design.md → ...hive/2026-03-09-quick-chat-mode-design.md b/...klog/2026-03-09-quick-chat-mode-design.md → ...hive/2026-03-09-quick-chat-mode-design.md
@@ -25,3 +25,7 @@ Design document at `docs/design/quick-chat-mode.md` exploring five approaches:
 ## Status
 
 Complete — design document written at `docs/design/quick-chat-mode.md`.
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: Design-only task, all 5 criteria checked; approaches since built (sam-session DO, project-agent, Instant sessions)._
diff --git a/tasks/archive/2026-03-12-fix-workspace-callback-auth-middleware-leak.md b/tasks/archive/2026-03-12-fix-workspace-callback-auth-middleware-leak.md
@@ -43,4 +43,4 @@ The VM agent sends Bearer JWT tokens for callbacks, but `requireAuth()` expects
 - `apps/api/src/routes/workspaces/lifecycle.ts:189-306` — callback-auth routes
 - `apps/api/src/routes/workspaces/runtime.ts` — more callback-auth routes
 - `apps/api/src/middleware/auth.ts:44` — "Authentication required" error source
-- `tasks/backlog/2026-03-12-provisioning-failed-callback-401.md` — initial bug report
+- `tasks/archive/2026-03-12-provisioning-failed-callback-401.md` — initial bug report
diff --git a/...03-12-provisioning-failed-callback-401.md → ...03-12-provisioning-failed-callback-401.md b/...03-12-provisioning-failed-callback-401.md → ...03-12-provisioning-failed-callback-401.md
@@ -38,3 +38,7 @@ Observed during production verification of the same-zone routing fix. The route
 - `docs/notes/2026-03-12-same-zone-routing-postmortem.md`
 - `apps/api/src/routes/workspaces.ts` — provisioning-failed handler
 - `apps/api/src/durable-objects/task-runner.ts` — alarm-based state machine
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #325 (9c7875b8c) same-day fix; route uses callback JWT only (lifecycle.ts:580-583); tests workspace-callback-auth-routing.test.ts:157,202._
diff --git a/...26-03-14-fix-mistral-vibe-acp-metadata.md → ...26-03-14-fix-mistral-vibe-acp-metadata.md b/...26-03-14-fix-mistral-vibe-acp-metadata.md → ...26-03-14-fix-mistral-vibe-acp-metadata.md
@@ -49,3 +49,7 @@ Monitor the [mistral-vibe releases](https://github.com/mistralai/mistral-vibe/re
 - [Mistral Vibe GitHub](https://github.com/mistralai/mistral-vibe)
 - [DeepWiki Config Reference](https://deepwiki.com/mistralai/mistral-vibe/8.1-configuration-reference)
 - [Reverse-engineered config.toml guide](https://gist.github.com/chris-hatton/6e1a62be8412473633f7ef02d067547d)
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #386 (c3a190e7d): ACP ClientInfo + VIBE_CLIENT_* (gateway.go:1136-1142) and generated ~/.vibe/config.toml aliases (vibe_config.go:45-143)._
diff --git a/tasks/archive/2026-03-14-lightweight-workspace-profile-tests.md b/tasks/archive/2026-03-14-lightweight-workspace-profile-tests.md
@@ -61,6 +61,6 @@ The lightweight workspace profile feature (`WorkspaceProfile = 'full' | 'lightwe
 ## References
 
 - Design doc: `docs/design/quick-chat-mode.md`
-- Prior task: `tasks/backlog/2026-03-09-quick-chat-mode-design.md`
+- Prior task: `tasks/archive/2026-03-09-quick-chat-mode-design.md`
 - VM agent contract: `packages/shared/src/vm-agent-contract.ts`
 - Rule 10 (e2e verification): `.claude/rules/10-e2e-verification.md`
diff --git a/tasks/archive/2026-03-14-mistral-vibe-default-to-large-model.md b/tasks/archive/2026-03-14-mistral-vibe-default-to-large-model.md
@@ -42,5 +42,5 @@ Additionally, a pre-existing test (`TestGetAgentExtraEnvVars_MistralVibe`) expec
 
 - `packages/vm-agent/internal/acp/gateway.go` — model env var mapping, config generation
 - `packages/vm-agent/internal/acp/session_host.go` — agent startup flow
-- `tasks/backlog/2026-03-14-fix-mistral-vibe-acp-metadata.md` — related metadata fix task
+- `tasks/archive/2026-03-14-fix-mistral-vibe-acp-metadata.md` — related metadata fix task
 - [Mistral Models Documentation](https://docs.mistral.ai/getting-started/models/)
diff --git a/...6-03-18-docker-exec-env-token-exposure.md → ...6-03-18-docker-exec-env-token-exposure.md b/...6-03-18-docker-exec-env-token-exposure.md → ...6-03-18-docker-exec-env-token-exposure.md
@@ -20,3 +20,7 @@ Discovered during security audit. The main agent process startup uses `-e` flags
 
 - `packages/vm-agent/internal/acp/process.go:150-152`
 - Security audit finding: HIGH severity
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #516 (0cd0fc6e8): /dev/shm 0600 --env-file (process.go:127-160,276-309); tests process_test.go:160-214 assert secrets never in args._
diff --git a/tasks/archive/2026-03-19-ideas-page-and-ideation-system.md b/tasks/archive/2026-03-19-ideas-page-and-ideation-system.md
@@ -113,4 +113,4 @@ During brainstorming, agents can produce artifacts — Playwright screenshots, r
 
 - `tasks/backlog/2026-03-19-graph-execution-model.md` — longer-term task decomposition and graph execution
 - `tasks/backlog/2026-03-18-code-context-for-task-submission.md` — complementary: how context flows into task submission
-- `tasks/backlog/2026-03-09-quick-chat-mode-design.md` — serverless chat was considered and deferred in favor of VM-backed brainstorming
+- `tasks/archive/2026-03-09-quick-chat-mode-design.md` — serverless chat was considered and deferred in favor of VM-backed brainstorming
diff --git a/...x-codex-mcp-streamable-http-compliance.md → ...x-codex-mcp-streamable-http-compliance.md b/...x-codex-mcp-streamable-http-compliance.md → ...x-codex-mcp-streamable-http-compliance.md
@@ -137,3 +137,7 @@ Claude Code and Mistral Vibe can use the same SAM MCP server successfully, so th
 - `tasks/archive/2026-04-02-fix-codex-acp-home-directory-resolution.md`
 - OpenAI Codex config reference
 - MCP Streamable HTTP lifecycle and transport specs
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as superseded (not built as written). Evidence: Shipped as PR #601 under tasks/archive/2026-04-03-fix-mcp-streamable-http-compliance.md._
diff --git a/tasks/archive/2026-04-03-fix-mcp-streamable-http-compliance.md b/tasks/archive/2026-04-03-fix-mcp-streamable-http-compliance.md
@@ -49,4 +49,4 @@ SAM's `/mcp` endpoint treats all JSON-RPC messages as requests. When Codex sends
 
 - `apps/api/src/routes/mcp/index.ts`
 - `apps/api/src/routes/mcp/_helpers.ts`
-- `tasks/backlog/2026-04-02-fix-codex-mcp-streamable-http-compliance.md`
+- `tasks/archive/2026-04-02-fix-codex-mcp-streamable-http-compliance.md`
diff --git a/...11-fix-flaky-useAvailableCommands-test.md → ...11-fix-flaky-useAvailableCommands-test.md b/...11-fix-flaky-useAvailableCommands-test.md → ...11-fix-flaky-useAvailableCommands-test.md
@@ -12,3 +12,7 @@
 ## Acceptance Criteria
 - [ ] Fix the timing issue in the test (likely needs a `waitFor` around the final assertion)
 - [ ] Test passes reliably in CI with coverage enabled
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as superseded (not built as written). Evidence: Proposed fix landed (25f329b88, #694); root cause owned by tasks/backlog/2026-07-04-fix-flaky-tests-at-root.md, which says to archive this file._
diff --git a/...backlog/2026-05-05-debug-package-fixes.md → ...archive/2026-05-05-debug-package-fixes.md b/...backlog/2026-05-05-debug-package-fixes.md → ...archive/2026-05-05-debug-package-fixes.md
@@ -141,3 +141,7 @@ The error reporter sends to `/api/nodes/{nodeId}/errors` with a Bearer token. If
 - JWT service: `apps/api/src/services/jwt.ts`
 - Node provisioning: `apps/api/src/services/nodes.ts`
 - CI build: `.github/workflows/deploy-reusable.yml:630`
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: All seven fix groups landed via #901 (template.ts mirror script, 15-min timeout), #966 (callback 401 + logged bodies), #1010 (cloud-init schema), VERSION pinned in deploy-reusable.yml:1057._
diff --git a/tasks/archive/2026-05-05-devcontainer-network-resilience.md b/tasks/archive/2026-05-05-devcontainer-network-resilience.md
@@ -2,7 +2,7 @@
 
 **Created**: 2026-05-05
 **Priority**: CRITICAL
-**Related**: `tasks/backlog/2026-05-05-debug-package-fixes.md` (Issues 1-3)
+**Related**: `tasks/archive/2026-05-05-debug-package-fixes.md` (Issues 1-3)
 
 ## Problem Statement
 
@@ -77,7 +77,7 @@ User wants lightweight containers to support Docker usage with fast boot via pri
 ## References
 
 - Failed task: `01KQVADC1ZF9ESQH70KWJDY7FB` (workspace timeout after apt failures)
-- Debug package analysis: `tasks/backlog/2026-05-05-debug-package-fixes.md`
+- Debug package analysis: `tasks/archive/2026-05-05-debug-package-fixes.md`
 - Cloud-init template: `packages/cloud-init/src/template.ts`
 - VM agent bootstrap: `packages/vm-agent/internal/bootstrap/bootstrap.go`
 - Node provisioning: `apps/api/src/services/nodes.ts`
diff --git a/...05-fix-chat-message-loading-regression.md → ...05-fix-chat-message-loading-regression.md b/...05-fix-chat-message-loading-regression.md → ...05-fix-chat-message-loading-regression.md
@@ -51,3 +51,7 @@ PR #874 ("Fix oversized chat session message loads", May 1st) introduced two com
 - PR #874: `091f2b67` — the regression commit
 - `packages/shared/src/constants/sam.ts` — SAM history limit constants
 - `docs/notes/2026-03-17-chat-message-duplication-report.md` — related message handling
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #898 did every item; the 3000 default was deliberately replaced by paging in #2165._
diff --git a/tasks/archive/2026-05-12-do-only-chat-typewriter.md b/tasks/archive/2026-05-12-do-only-chat-typewriter.md
@@ -81,4 +81,4 @@ TypewriterText animates batches -> feels like streaming
 
 ## References
 - React error #185: infinite render loop from dual WebSocket sources
-- `tasks/backlog/2026-03-06-unify-project-chat-through-do-streaming.md` — earlier proposal for DO-only streaming
+- `tasks/archive/2026-03-06-unify-project-chat-through-do-streaming.md` — earlier proposal for DO-only streaming
diff --git a/...klog/2026-05-12-fix-vm-agent-stability.md → ...hive/2026-05-12-fix-vm-agent-stability.md b/...klog/2026-05-12-fix-vm-agent-stability.md → ...hive/2026-05-12-fix-vm-agent-stability.md
@@ -104,3 +104,7 @@ Debug package analysis revealed four interconnected production issues that cause
 - `docs/notes/2026-03-25-deployment-identity-token-middleware-leak-postmortem.md`
 - `.claude/rules/06-api-patterns.md` (Hono middleware scoping)
 - `.claude/rules/31-migration-safety.md`
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: Timers #968, dispatch dedup #1033 + VM idempotency #1031, callback extraction + MCP sliding window #966._
diff --git a/...2-vm-agent-cloud-init-firewall-hygiene.md → ...2-vm-agent-cloud-init-firewall-hygiene.md b/...2-vm-agent-cloud-init-firewall-hygiene.md → ...2-vm-agent-cloud-init-firewall-hygiene.md
@@ -69,4 +69,8 @@ Debug package analysis revealed several cloud-init and firewall hygiene issues t
 - `packages/cloud-init/src/template.ts` — cloud-init template
 - `packages/cloud-init/tests/generate.test.ts` — existing tests
 - `packages/vm-agent/internal/provision/provision.go` — vm-agent provisioning
-- `tasks/backlog/2026-05-12-fix-vm-agent-stability.md` — broader task (this is a subset)
+- `tasks/archive/2026-05-12-fix-vm-agent-stability.md` — broader task (this is a subset)
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #968 (cbd2ad1d3): template.ts:35-39, :632-650; tests generate.test.ts:1486-1508,1548-1570._
diff --git a/tasks/archive/2026-05-12-vm-agent-container-recovery.md b/tasks/archive/2026-05-12-vm-agent-container-recovery.md
@@ -58,7 +58,7 @@ Some related work landed in PR #966 and PR #968, but the VM-agent resilience gap
 - Bridge IP cache entries are scoped to the container ID they were resolved from, so fallback containers cannot inherit stale network metadata.
 - Port scanning now treats scan failures as possible stale-container signals, clears the cached ID, re-runs the configured resolver, and emits `port.scanner_container_changed` when a replacement is found.
 - Provider apt mirror injection now backs up source files, rewrites them, validates the mirror through `apt-get update` using temporary list/cache directories, and restores the original sources if validation fails.
-- Root password expiration and cloud-init schema warnings are not directly actionable in this PR: no repo-controlled `chpasswd`/root password template was found, and the existing active task `tasks/backlog/2026-05-12-vm-agent-cloud-init-firewall-hygiene.md` already records the remaining cloud-init/firewall hygiene track.
+- Root password expiration and cloud-init schema warnings are not directly actionable in this PR: no repo-controlled `chpasswd`/root password template was found, and the existing active task `tasks/archive/2026-05-12-vm-agent-cloud-init-firewall-hygiene.md` already records the remaining cloud-init/firewall hygiene track.
 
 ## Acceptance Criteria
 

diff --git a/...-27-workspace-forward-local-port-remap.md → ...-27-workspace-forward-local-port-remap.md b/...-27-workspace-forward-local-port-remap.md → ...-27-workspace-forward-local-port-remap.md
@@ -16,3 +16,7 @@
 - [ ] `sam workspace <id> forward --port 3000 --local 8080` binds to localhost:8080 and proxies to remote port 3000
 - [ ] Mismatched `--port` and `--local` counts produce a clear error
 - [ ] Tests cover the remapping logic
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #1370 (2686df375) added --local-port (workspace.go:151-164,233-254) with tests._
diff --git a/tasks/archive/2026-05-27-workspace-port-forwarding-command.md b/tasks/archive/2026-05-27-workspace-port-forwarding-command.md
@@ -73,7 +73,7 @@ sam workspace <workspaceId> ports                 # list detected ports
   - Log proxied requests to stderr
   - Handle SIGINT/SIGTERM for graceful shutdown
 - [x] Implement `runWorkspacePorts()` — list detected ports (text + JSON output)
-- [ ] ~~Add `--local` flag support for port remapping~~ — deferred to `tasks/backlog/2026-05-27-workspace-forward-local-port-remap.md`
+- [ ] ~~Add `--local` flag support for port remapping~~ — deferred to `tasks/archive/2026-05-27-workspace-forward-local-port-remap.md`
 
 ### CLI: Help Text & Output
 - [x] Update `helpText()` in `run.go` to include workspace commands

diff --git a/tasks/archive/2026-06-13-app-deployment-system-status.md b/tasks/archive/2026-06-13-app-deployment-system-status.md
@@ -69,11 +69,11 @@ flowchart LR
 
 ```mermaid
 flowchart TD
-    A["Per-env host-port offset collision<br/>buildDeploymentRouteTargets uses route index only;<br/>two envs on one node both grab 35000.<br/>engine.go skips composeDown of prior release.<br/>(tasks/backlog/2026-06-13-deployment-per-env-host-port-offset.md)"]:::open
-    B["Compose preview omits route-target ports<br/>GET .../compose renders without routeTargets;<br/>preview != real node payload.<br/>(tasks/backlog/2026-06-13-compose-preview-endpoint-route-targets.md)"]:::open
+    A["Per-env host-port offset collision<br/>buildDeploymentRouteTargets uses route index only;<br/>two envs on one node both grab 35000.<br/>engine.go skips composeDown of prior release.<br/>(tasks/archive/2026-06-13-deployment-per-env-host-port-offset.md)"]:::open
+    B["Compose preview omits route-target ports<br/>GET .../compose renders without routeTargets;<br/>preview != real node payload.<br/>(tasks/archive/2026-06-13-compose-preview-endpoint-route-targets.md)"]:::open
     C["Compose-parser test coverage<br/>(tasks/backlog/2026-06-11-compose-parser-test-coverage.md)"]:::open
     D["Deployment-provisioning route tests<br/>(tasks/backlog/2026-06-12-deployment-provisioning-route-tests.md)"]:::open
-    E["docker-exec env token exposure<br/>(tasks/backlog/2026-03-18-docker-exec-env-token-exposure.md)"]:::open
+    E["docker-exec env token exposure<br/>(tasks/archive/2026-03-18-docker-exec-env-token-exposure.md)"]:::open
     F["Route-level error message leakage<br/>(tasks/backlog/2026-04-10-route-level-error-message-leakage.md)"]:::open
     classDef open fill:#3a2f1b,stroke:#ffb300,color:#fff8e1;
 ```

diff --git a/...compose-preview-endpoint-route-targets.md → ...compose-preview-endpoint-route-targets.md b/...compose-preview-endpoint-route-targets.md → ...compose-preview-endpoint-route-targets.md
@@ -28,3 +28,7 @@ make public routes work.
       intentionally omitted from the preview.
 - [ ] Test asserting preview output matches node-apply output for a manifest with a public
       route (or asserting the documented difference).
+
+---
+
+_Reconciled 2026-09-30 (weekly queue reconciliation): moved from `tasks/backlog/` to `tasks/archive/` as shipped. Evidence: #1312 (8ccbcee41): deployment-releases.ts:353-376 passes routeTargets matching the apply payload; tests compose-preview-parity.test.ts:110,158,231._