chore: reconcile stale namespace debt trackers

Author: thegeronimo

…izer-vault-one-year-return-estimation.md …izer-vault-one-year-return-estimation.mddocs/exec-plans/active/2026-04-30-optimizer-vault-one-year-return-estimation.md renamed to docs/exec-plans/completed/2026-04-30-optimizer-vault-one-year-return-estimation.md docs/exec-plans/active/2026-04-30-optimizer-vault-one-year-return-estimation.md renamed to docs/exec-plans/completed/2026-04-30-optimizer-vault-one-year-return-estimation.md

@@ -1,6 +1,6 @@
 ---
 owner: portfolio
-status: active
+status: completed
 created: 2026-04-30
 source_of_truth: false
 tracked_issue: hyperopen-0amu
@@ -35,14 +35,15 @@ After this change, optimizer vault return estimation should follow the same boun
 - [x] (2026-04-30 18:49Z) Re-ran `npm run check` after refreshing the active ExecPlan; docs lint passed and the command now fails only on the known pre-existing namespace-size issues in `src/hyperopen/views/portfolio/optimize/frontier_chart.cljs` and `test/hyperopen/views/portfolio/optimize/results_panel_test.cljs`, both outside this ticket’s write scope.
 - [x] (2026-04-30 18:49Z) Re-ran `npm test` and `npm run test:websocket`; both passed after the follow-up patch.
 - [x] (2026-04-30 18:53Z) Parent thread independently re-ran the focused optimizer command; it passed with 16 tests, 92 assertions, 0 failures, and 0 errors.
-- [x] (2026-04-30 18:53Z) Parent thread independently re-ran `npm test`, `npm run test:websocket`, `npm run lint:namespace-boundaries`, and `npm run lint:namespace-sizes`. `npm test`, websocket tests, and namespace boundaries passed. `lint:namespace-sizes` still fails only on unrelated namespace-size guardrails outside this ticket.
+- [x] (2026-04-30 18:53Z) Parent thread independently re-ran `npm test`, `npm run test:websocket`, `npm run lint:namespace-boundaries`, and `npm run lint:namespace-sizes`. `npm test`, websocket tests, and namespace boundaries passed. At that time, `lint:namespace-sizes` still failed only on unrelated namespace-size guardrails outside this ticket.
 - [x] (2026-04-30 18:53Z) Created follow-up `bd` issue `hyperopen-qgmq` for the unrelated namespace-size gate failures that keep `npm run check` from completing.
 - [x] (2026-04-30 19:00Z) Added a second RED layer for sparse-calendar annualization. The focused command now fails because `align-history-inputs` does not yet emit `:return-intervals`, and `estimate-expected-returns` still annualizes two half-year `+10%` vault observations to `36.5` instead of about `0.21`.
 - [x] (2026-04-30 19:13Z) Implemented `:return-intervals` on aligned optimizer history and elapsed-time-aware geometric annualization for sparse valid intervals. Added a guard regression proving one-day candle histories keep the established arithmetic daily estimator.
 - [x] (2026-04-30 19:13Z) Re-ran focused optimizer coverage with `history-loader-test`, `request-builder-test`, `domain.returns-test`, and `engine-test`; it passed with 36 tests, 186 assertions, 0 failures, and 0 errors.
-- [x] (2026-04-30 19:13Z) Re-ran the required gates after the final sparse-interval patch. `npm test`, `npm run test:websocket`, and `npm run lint:namespace-boundaries` passed. `npm run check` and direct `npm run lint:namespace-sizes` still fail only on the known unrelated namespace-size blocker tracked by `hyperopen-qgmq`.
-- [ ] Close `hyperopen-0amu` only after the unrelated namespace-size gate blocker is resolved or explicitly accepted as a blocker for this ticket.
-- [ ] Move this ExecPlan out of `active/` after ticket close-out so docs lint no longer treats it as stale completed work.
+- [x] (2026-04-30 19:13Z) Re-ran the required gates after the final sparse-interval patch. `npm test`, `npm run test:websocket`, and `npm run lint:namespace-boundaries` passed. At that time, `npm run check` and direct `npm run lint:namespace-sizes` still failed only on the known unrelated namespace-size blocker tracked by `hyperopen-qgmq`.
+- [x] (2026-05-01 17:59Z) Reconciled the unrelated namespace-size blocker: `src/hyperopen/views/portfolio/optimize/frontier_chart.cljs` is now `482` lines, `test/hyperopen/views/portfolio/optimize/results_panel_test.cljs` is now `87` lines, and `npm run lint:namespace-sizes` passes.
+- [x] (2026-05-01 18:00Z) Closed `hyperopen-0amu` after the stale blocker was reconciled.
+- [x] (2026-05-01 18:00Z) Moved this ExecPlan out of `active/` after ticket close-out so docs lint no longer treats it as stale completed work.
 
 ## Surprises & Discoveries
 
@@ -67,8 +68,8 @@ After this change, optimizer vault return estimation should follow the same boun
 - Observation: the stronger follow-up regression exposed that the first fix still encoded the wrong tie-breaker, not the wrong derivation.
   Evidence: before the follow-up patch, `preferred-vault-summary` required the derived one-year summary to have at least as many observations as the shorter direct fallback. The strengthened focused command failed with the direct month calendar `[1772236800000 1773446400000 1774656000000 1776124800000 1777507200000]` and about `-2%` vault returns instead of the expected derived one-year rows.
 
-- Observation: the remaining `npm run check` blocker is unrelated namespace-size governance, not source correctness for this fix.
-  Evidence: parent-thread verification reached `npm run lint:namespace-sizes` and reported `[missing-size-exception] src/hyperopen/views/portfolio/optimize/frontier_chart.cljs - namespace has 502 lines` and `[size-exception-exceeded] test/hyperopen/views/portfolio/optimize/results_panel_test.cljs - namespace has 544 lines; exception allows at most 540`. Follow-up `bd` issue `hyperopen-qgmq` tracks that blocker.
+- Observation: the former `npm run check` blocker was unrelated namespace-size governance, not source correctness for this fix, and it has since been reconciled.
+  Evidence: parent-thread verification on 2026-04-30 reached `npm run lint:namespace-sizes` and reported `[missing-size-exception] src/hyperopen/views/portfolio/optimize/frontier_chart.cljs - namespace has 502 lines` and `[size-exception-exceeded] test/hyperopen/views/portfolio/optimize/results_panel_test.cljs - namespace has 544 lines; exception allows at most 540`. The 2026-05-01 reconciliation confirmed `frontier_chart.cljs` is now `482` lines, `results_panel_test.cljs` is now `87` lines, and `npm run lint:namespace-sizes` passes.
 
 - Observation: choosing the correct one-year vault window is necessary but insufficient when that window is sparse.
   Evidence: with a derived one-year vault calendar of `[2025-04-30, 2025-10-30, 2026-04-30]`, the optimizer return series contains two half-year returns. `src/hyperopen/portfolio/optimizer/domain/returns.cljs` still multiplies their mean by `365`, which treats each half-year observation like one daily return and can inflate expected returns by roughly two orders of magnitude.
@@ -106,7 +107,7 @@ After this change, optimizer vault return estimation should follow the same boun
 
 Implemented the selection layer as planned with a small boundary-safe extraction, then tightened by follow-up regressions. The optimizer now derives a bounded one-year vault summary from all-time account/PnL history when there is no direct `:one-year`, the cutoff has a real anchor, and the derived window meets the minimum useful observation threshold. Direct `:one-year` still wins, but shorter direct fallback summaries no longer override a complete derived one-year window merely because they have more rows. The optimizer history contract now also carries common-calendar `:return-intervals`, and expected-return estimation uses elapsed-time geometric annualization for sparse valid intervals so two half-year `+10%` vault observations estimate about `+21%` annualized rather than `+3650%`.
 
-The focused regressions pass after the final sparse-interval patch, including the daily-estimator guard. Parent-thread verification also passed `npm test`, `npm run test:websocket`, and `npm run lint:namespace-boundaries`. `npm run check` is blocked by unrelated namespace-size failures in `src/hyperopen/views/portfolio/optimize/frontier_chart.cljs` and `test/hyperopen/views/portfolio/optimize/results_panel_test.cljs`; follow-up `hyperopen-qgmq` tracks that existing gate issue. The implementation itself no longer adds a validation blocker of its own.
+The focused regressions pass after the final sparse-interval patch, including the daily-estimator guard. Parent-thread verification also passed `npm test`, `npm run test:websocket`, and `npm run lint:namespace-boundaries`. The unrelated namespace-size blocker that originally kept `hyperopen-0amu` open was later retired by the optimizer namespace debt cleanup and reconciled in `hyperopen-oy7v`; `hyperopen-qgmq` is no longer an active gate blocker. The implementation itself no longer adds a validation blocker of its own.
 
 ## Context and Orientation
 

docs/exec-plans/completed/2026-05-01-stale-bd-namespace-debt-reconciliation.md

@@ -0,0 +1,98 @@
+---
+owner: platform
+status: completed
+created: 2026-05-01
+source_of_truth: false
+tracked_issue: hyperopen-oy7v
+---
+
+# Stale Namespace Debt Tracker Reconciliation
+
+This ExecPlan is a living document. The sections `Progress`, `Surprises & Discoveries`, `Decision Log`, and `Outcomes & Retrospective` must be kept current while work proceeds.
+
+This document follows `/hyperopen/AGENTS.md`, `/hyperopen/docs/PLANS.md`, and `/hyperopen/docs/WORK_TRACKING.md`. The live `bd` issue is `hyperopen-oy7v`; `bd` remains the lifecycle source of truth.
+
+## Purpose / Big Picture
+
+Reconcile stale namespace-size debt tracker state that is now creating agent-comprehension drag. The work is tracker and planning hygiene only: close stale `bd` issues whose named blockers are resolved, move completed plan context out of `active/`, and verify the current checkout with docs and namespace-size gates.
+
+After this work, agents should no longer see `hyperopen-qgmq` as an open namespace-size blocker, `hyperopen-0amu` should no longer be held open by that stale blocker, and `hyperopen-qcuq` should no longer appear in progress after the account-info exception wave completed.
+
+## Progress
+
+- [x] (2026-05-01 17:57Z) Created and claimed `bd` issue `hyperopen-oy7v`.
+- [x] (2026-05-01 17:58Z) Created this active ExecPlan.
+- [x] (2026-05-01 17:59Z) Confirmed current evidence for the stale issues: `frontier_chart.cljs` is `482` lines, `results_panel_test.cljs` is `87` lines, `order_history.cljs` is `486` lines, the account-info/optimizer paths are absent from `dev/namespace_size_exceptions.edn`, and `npm run lint:namespace-sizes` passed.
+- [x] (2026-05-01 18:00Z) Updated the stale optimizer plan with reconciliation evidence and moved it to `docs/exec-plans/completed/2026-04-30-optimizer-vault-one-year-return-estimation.md`.
+- [x] (2026-05-01 18:00Z) Closed stale `bd` issues `hyperopen-qgmq`, `hyperopen-qcuq`, and `hyperopen-0amu` with explicit reasons.
+- [x] (2026-05-01 18:03Z) Ran validation commands: `npm run lint:docs`, `npm run lint:namespace-sizes`, and `npm run check` passed after restoring missing locked dependencies with `npm install`.
+- [x] (2026-05-01 18:03Z) Moved this ExecPlan to completed and closed `hyperopen-oy7v`.
+
+## Surprises & Discoveries
+
+- Observation: `hyperopen-qgmq` is stale in the current checkout.
+  Evidence: `wc -l` reports `src/hyperopen/views/portfolio/optimize/frontier_chart.cljs` at `482` lines and `test/hyperopen/views/portfolio/optimize/results_panel_test.cljs` at `87` lines, and `npm run lint:namespace-sizes` exits `0`.
+- Observation: `hyperopen-qcuq` is stale in the current checkout.
+  Evidence: `rg -n "account_info|account-info" dev/namespace_size_exceptions.edn` returns no entries, and the largest current account-info namespace is `src/hyperopen/views/account_info/tabs/order_history.cljs` at `486` lines.
+- Observation: `hyperopen-0amu` had implementation evidence but remained in progress because its active ExecPlan waited for the now-stale `hyperopen-qgmq` blocker.
+  Evidence: `/hyperopen/docs/exec-plans/completed/2026-04-30-optimizer-vault-one-year-return-estimation.md` records passed focused optimizer coverage, `npm test`, `npm run test:websocket`, and `npm run lint:namespace-boundaries`; this reconciliation closed `hyperopen-qgmq` first, then closed `hyperopen-0amu`.
+- Observation: this worktree's `node_modules` was incomplete even though the lockfile declared the needed packages.
+  Evidence: the first `npm run check` failed in `npm run test:multi-agent` with missing `zod` and `smol-toml`; `package.json` and `package-lock.json` already declared both packages, `npm install` restored them without package metadata diffs, and the rerun of `npm run check` passed.
+
+## Decision Log
+
+- Decision: treat this as lifecycle reconciliation, not as a source-code refactor.
+  Rationale: the source and test splits already landed in completed plans, and the current namespace-size gate passes. The remaining work is stale issue and plan metadata.
+  Date/Author: 2026-05-01 / Codex
+- Decision: close `hyperopen-0amu` after replacing stale blocker language with final validation evidence.
+  Rationale: the active optimizer plan already records the implementation outcome and focused regressions. Keeping it open because of a resolved namespace-size blocker misrepresents the current repo state.
+  Date/Author: 2026-05-01 / Codex
+
+## Outcomes & Retrospective
+
+The stale namespace-debt tracker state was reconciled. `hyperopen-qgmq`, `hyperopen-qcuq`, and `hyperopen-0amu` are now closed with reasons tied to current evidence. The old optimizer one-year return ExecPlan was updated with the reconciliation evidence and moved from `active/` to `completed/`.
+
+No source code changed. The only file edits were planning artifacts, plus local `node_modules` restoration from the existing lockfile to make the full check command runnable in this worktree.
+
+Validation passed:
+
+- `npm run lint:docs`
+- `npm run lint:namespace-sizes`
+- `npm run check`
+
+## Context and Orientation
+
+The stale tracker items came from two completed namespace-size cleanup waves:
+
+- `hyperopen-qgmq` was created from `hyperopen-0amu` when `frontier_chart.cljs` and `results_panel_test.cljs` briefly blocked `npm run check`. The completed optimizer namespace-debt plan later reduced `frontier_chart.cljs` to `482` lines and `results_panel_test.cljs` to `87` lines, with no active exception needed.
+- `hyperopen-qcuq` tracked the account-info surface exception wave. The completed account-info plan records that every targeted account-info entry was removed from `dev/namespace_size_exceptions.edn`, and current line counts confirm the account-info files are below the default limit.
+- `hyperopen-0amu` was still in progress only because its active ExecPlan said to close it after the unrelated namespace-size blocker was resolved or explicitly accepted.
+
+The relevant files are:
+
+- `docs/exec-plans/completed/2026-04-30-optimizer-vault-one-year-return-estimation.md`
+- `docs/exec-plans/completed/2026-04-13-account-info-surface-oversized-exception-retirement.md`
+- `docs/exec-plans/completed/2026-05-01-portfolio-optimizer-namespace-debt-retirement.md`
+- `docs/exec-plans/completed/2026-05-01-stale-bd-namespace-debt-reconciliation.md`
+- `dev/namespace_size_exceptions.edn`
+
+## Plan of Work
+
+1. Confirm evidence with `wc -l`, `rg`, and `npm run lint:namespace-sizes`.
+2. Edit `docs/exec-plans/active/2026-04-30-optimizer-vault-one-year-return-estimation.md` so its progress and retrospective reflect that the stale namespace-size blocker has been reconciled.
+3. Move `docs/exec-plans/active/2026-04-30-optimizer-vault-one-year-return-estimation.md` to `docs/exec-plans/completed/2026-04-30-optimizer-vault-one-year-return-estimation.md` and change its frontmatter status to `completed`.
+4. Close `hyperopen-qgmq` as stale/resolved by later optimizer namespace debt retirement.
+5. Close `hyperopen-qcuq` as completed based on the account-info completed plan and current exception inventory.
+6. Close `hyperopen-0amu` as completed after the stale blocker has been removed from active plan state.
+7. Update this ExecPlan outcomes, run `npm run lint:docs`, `npm run lint:namespace-sizes`, and `npm run check`, then move this plan to `completed/` and close `hyperopen-oy7v`.
+
+## Acceptance Criteria
+
+- `bd show hyperopen-qgmq --json` reports `status: closed`.
+- `bd show hyperopen-qcuq --json` reports `status: closed`.
+- `bd show hyperopen-0amu --json` reports `status: closed`.
+- No stale `hyperopen-qgmq` blocker text remains in active ExecPlans.
+- No active ExecPlan references only closed work.
+- `npm run lint:docs` passes.
+- `npm run lint:namespace-sizes` passes.
+- `npm run check` passes.