From ddd55a6ce425c82d61f567ebe5085762df646141 Mon Sep 17 00:00:00 2001 From: Chris0Jeky Date: Tue, 8 Sep 2026 02:44:08 +0100 Subject: [PATCH 1/2] docs: record September parallel delivery checkpoint --- OUTSTANDING_TASKS.md | 4 + docs/IMPLEMENTATION_MASTERPLAN.md | 33 ++++- docs/STATUS.md | 11 +- .../2026-09-08-parallel-issue-wave.md | 116 ++++++++++++++++++ 4 files changed, 162 insertions(+), 2 deletions(-) create mode 100644 docs/analysis/2026-09-08-parallel-issue-wave.md diff --git a/OUTSTANDING_TASKS.md b/OUTSTANDING_TASKS.md index bee71ea2b..14e9fdc67 100644 --- a/OUTSTANDING_TASKS.md +++ b/OUTSTANDING_TASKS.md @@ -173,6 +173,10 @@ The maintainer directed (2026-08-30) that the repository goes **private for the --- +### J.1. September 8 control-path review checkpoint + +- [ ] **SC-10 follow-through — maintainer review of the current dependency/CI queue and acknowledgement of the #2772 merge error.** Review #2769 (npm minor updates), #2803 (the coherent Vitest 5 trio), #2791 (nightly observer), and #2792 (CI trust contract) at their current verified heads before merge. `ci/policy.v1.json` explicitly includes frontend package manifests/locks and `backend/Directory.Packages.props` as control paths. The coordinator merged #2772 at `d8fc1ceca3e33bef6ef9d315d79a5e996002ae18` without the required maintainer review, despite green CI and independent review; the error is disclosed on #2772 (comment 5577569078) and #2337 (5577569315). No retrospective approval, acknowledgement, rollback decision, or changed authority is inferred. The checked SC-10 row above covers its historical named batch only. Refresh exact heads, bases, CI and remaining review budgets before acting; the three individual Vitest PRs #2770/#2771/#2773 remain open until their replacement is authorized and merged. + ## K. v0.3 residual decision batch (2026-09-05, from the alpha lane's read-only audit of 15 milestone issues) — human actions Source: the alpha lane audited 15 open v0.3 issues on 2026-09-04 against `main` `61e94f672` to `8c511205d`, each audit adversarially re-verified read-only, and handed the coordinator the gates that need a maintainer answer. Everything agent-decidable from the same audit is already queued on the lanes without a ruling (#2215, #2214, #1307 batch-approve parity, #2007 AC5+AC6, #1968 Legacy-truthful shortcut map, #2009 contrast-guard pins, #1284 view-level regression, #1961 board-store dedupe, #2501 MEDIUM-2). Answer by letter on the issue named in each item, or in one reply here; each audit item says what the answer unblocks and names a proposed default, which is the direction the agents would recommend, not authorization to act while the item is unanswered (D-12 was ruled in-session on 2026-09-05 and is closed). Nothing below is built, closed, moved or re-titled until its letter is recorded here or on the issue (D-12 was ruled in-session on 2026-09-05; D-1 to D-11 and D-13 to D-15 were ruled in-session on 2026-09-06 through the guided walkthrough, each row carrying its letters). diff --git a/docs/IMPLEMENTATION_MASTERPLAN.md b/docs/IMPLEMENTATION_MASTERPLAN.md index 5adf43d59..ff7b63742 100644 --- a/docs/IMPLEMENTATION_MASTERPLAN.md +++ b/docs/IMPLEMENTATION_MASTERPLAN.md @@ -1,6 +1,6 @@ # Taskdeck Implementation Masterplan -Last Updated: 2026-09-07 +Last Updated: 2026-09-08
Planning Horizon: the revival waves in `docs/REVIVAL_PLAN.md` (truth + safety → transcript engine → open-beta launch → generalist expansion [Phase 4, ADR-0046 Accepted]) plus ADR-0051's bounded autonomous backlog lane, then a maintainer checkpoint on beta traction — _(historical: 2026-06-13→2026-07-10 this was the finite archive-pivot waves; before that an open "Next 8 to 12 weeks" release horizon)_ Companion Active Docs: @@ -65,6 +65,37 @@ behaviour. ## Dated delivery and governance updates (newest first) +## Delivery update (2026-09-08, parallel implementation and asynchronous review) + +The maintainer authorized concurrent issue delivery, including v0.4/v0.5 foundations, +with separate Terra review threads. Seven scoped implementation lanes were admitted; +the coordinator retained canonical documentation, project state, and merge judgment. +Capture edit-capability polling, Paper read-only keyboard behavior, inspector/dialog +focus, and the Processing-state API test isolation have landed through PRs #2796, +#2788, #2799 and #2801. Parent issues with broader acceptance remain open. + +CF-24A's first synthetic text corpus and deterministic per-kind scorer landed in +PR #2804 (21 Python tests plus hosted CI). #2319 remains open for schema-validation +and processor-attribution follow-through, expanded media, and measured processor +quality/latency/cost. The initial command executes no processor. + +PR #2805 completes #2418's resumable repair for historical Capture divergence +masked by later disposition timestamps. Version-zero backlog selection, immutable +asset append and a distinct v2 completion marker preserve truthful pending reads; +archived mismatches remain outstanding while healthy rows advance. PR #2806 also +completes #2777's shared frontend instruction parity corrections. + +The representation and processing-policy lanes implement their first contract slices; +runtime persistence, processing queues and runners remain separate acceptance. The +benchmark lane starts with synthetic text and explicit unavailable metrics. These +boundaries prevent foundation code from being mistaken for a completed v0.4/v0.5 +processing product. + +Control-path dependency PRs require the maintainer's own review under ADR-0066, +including frontend package manifests/locks and backend Directory.Packages.props. +The coordinator missed this requirement on merged PR #2772 and disclosed it on that +PR and #2337. Green CI and independent review do not supply the missing review. + ## Planning update (2026-09-07, transcript prompt v3) #2211 moves current generation, frontend provenance recognition and packaged acceptance to diff --git a/docs/STATUS.md b/docs/STATUS.md index c7eaee044..b406c3943 100644 --- a/docs/STATUS.md +++ b/docs/STATUS.md @@ -1,6 +1,6 @@ # Taskdeck Status (Source of Truth) -Last Updated: 2026-09-07 +Last Updated: 2026-09-08 **Authority.** This file owns *shipped reality* - what is built, verified, and running today. **Evidence and authority:** reconcile shipped-state claims against code, tests and current execution evidence. Applicable instructions and `.agent-harness/tier.json` govern authority; this file cannot grant or override it. @@ -8,6 +8,15 @@ Last Updated: 2026-09-07 **Execution plan** (phases, waves, ship gate, checkpoint) is owned by [`docs/REVIVAL_PLAN.md`](REVIVAL_PLAN.md). **History** - delivery records dated before 2026-07-01 - lives in [`docs/archive/status-history/`](archive/status-history/) and is non-authoritative. +September 8 parallel delivery wave (merged work; #2235): + +- Historical Capture text divergence masked by later Keep/Archive timestamps is repaired by PR #2805 (#2418). The additive `LegacyReconciliationVersion` column defaults old rows to zero, bounded SQL pages revisit them once, and successful reconciliation appends immutable superseding assets before stamping the current version. The distinct v2 completion marker ignores historical v1 success. Archived mismatches remain outstanding and readable through safe queue fallback while healthy rows progress; list/detail guards do not rely on timestamps alone for unresolved version-zero rows. The full backend gate passed 8,977 tests with five existing skips, followed by clean independent review and hosted CI. No existing private database or large-database timing was exercised. This supersedes the timestamp-only repair description in the original CF-01 record below. +- Shared frontend instructions now name the actual Claude adapter/import, runtime-specific search fallback and explicit PowerShell working directory (PR #2806, #2777). Documentation, syntax/path checks, independent review and required hosted checks passed; no runtime behavior or authority changed. +- CF-24A's first benchmark slice is available (PR #2804, #2319): nine synthetic text sources totaling 934 bytes, explicit origin/license/hash/reference metadata, a 16 KiB source-byte budget, and deterministic per-kind precision/recall/F1 scoring from supplied predictions. Twenty-one Python tests and the required hosted checks passed. The command does not run a processor; audio/image/PDF quality, latency, WER and cost are unmeasured. Schema-validation and persisted processor-identity limitations remain tracked on #2319, alongside the larger corpus acceptance. This establishes fixture/scoring tooling, not a release-quality result. +- Capture polling preserves the server's `canEditSuggestion` decision (PR #2796), reducing interrupted editing while keeping the server authoritative. Paper read-only keyboard behavior and dialog focus are corrected (PRs #2788 and #2799); the wider #1968, #1999 and #2090 acceptance remains open. The Processing-state capture API regression now disables its background triage worker and proves the persisted state before asserting rejection (PR #2801, #2798). +- These four slices each passed independent Terra review and their required hosted checks at the merged head. Local focused evidence is scoped to each PR; it is not a new full-suite count for current `main` or a packaged/live-provider acceptance claim. +- Sentry.AspNetCore 6.10.0 and Testcontainers.PostgreSql 4.15.0 landed in PR #2772 with green hosted CI and independent review. **Authority correction:** the coordinator missed the maintainer-own-review requirement for `backend/Directory.Packages.props`, a declared CI control path. The merge is disclosed on #2772 and #2337; no retrospective approval is inferred. New npm/Vitest and CI-control PRs remain subject to that review under [OUTSTANDING_TASKS.md](../OUTSTANDING_TASKS.md). + Transcript prompt identity (#2211, current implementation): - Current LLM transcript extraction records `llm-triage.v3`, including successful empty extraction, so the capture-reference-date semantics introduced by #2206 have their own provenance identity. The JSON shape remains schema v2; deterministic extraction keeps its existing identity. Historical `llm-triage.v2` payloads, schema and recorded provenance remain readable. The frontend classifier and current packaged acceptance checks move with the producer. This changes attribution, not review-first approval or Apply behavior. diff --git a/docs/analysis/2026-09-08-parallel-issue-wave.md b/docs/analysis/2026-09-08-parallel-issue-wave.md new file mode 100644 index 000000000..072079ee5 --- /dev/null +++ b/docs/analysis/2026-09-08-parallel-issue-wave.md @@ -0,0 +1,116 @@ +# September 8 parallel issue wave + +The maintainer authorized concurrent implementation, including v0.4/v0.5 work, +with independent Terra threads following review and fixes. This record covers a +bounded seven-issue wave and the existing PR queue. It does not declare a milestone +complete or accept a release. + +## Delivered and reviewed + +| PR | Delivered behavior | Merge commit | +| --- | --- | --- | +| #2796 | Preserve capture edit capability during polling | `ec0a1013ed65893f0af84445f2780f5a7bf23bc0` | +| #2788 | Paper read-only keyboard handling | `ca6bc39b87f3e182501beb9a1dd9776b557cf15c` | +| #2799 | Inspector-to-modal focus | `0ffb958247117c1be71d5588e5c1a8a18cb36cbe` | +| #2801 | Isolate the capture Processing-state API regression; closes #2798 | `d65bd64c470a8a0fbc8e841d136aa7c089488eb0` | +| #2802 | Preserve the previous session's dated handoff | `cbc26704ba10e66152bd2c0221735cf2cd3642ee` | +| #2804 | First synthetic text benchmark corpus and per-kind scorer | `72a181cf06495343aea7d35d2b89744d5555d89b` | +| #2805 | Versioned masked-capture repair; closes #2418 | `dfa12ea5a915cc920f9c302f27d12bf04592e733` | +| #2806 | Frontend instruction parity; closes #2777 | `0a02085527fa9e707529bb312e040a3f702c94b9` | +| #2772 | Sentry 6.10.0 and Testcontainers.PostgreSql 4.15.0; authority error below | `d8fc1ceca3e33bef6ef9d315d79a5e996002ae18` | + +Each had green hosted checks at the merged head and an independent Terra review. +The coordinator checked late comments once at the next milestone; no follow-up +defect was found in the product merges above. The dependency merge's missing +maintainer review is a separate failure of authority, not a failed test. + +## New issue slices and verification boundaries + +| Issue | Slice | Frozen source head and local evidence | +| --- | --- | --- | +| #2418 | Versioned repair for Capture divergence hidden by later Keep/Archive timestamps | `d4562fb92e791df9dc1457c74b19b255646f5a9c`; 45 Application and 16 SQLite/API focused checks, then full backend 8,977 passed / 5 existing skips | +| #2260 | CF06-1 immutable representation header, supersession edge and descriptor | `9fd6a69e257db7e91fbe40064767293e43901a86`; 21 Domain and 1 Application targeted checks, then full backend 8,995 passed / 5 existing skips; PR #2809 | +| #2257 | CF03-1 immutable processing policy and canonical digest | `ad02598a038bb0a969c66919db66a91ba2f59907`; 12 focused tests and full backend exit 0; final per-project totals not captured; PR #2811 | +| #2319 | Initial synthetic text corpus and per-kind scorer | `6c9bec284b1feaade2cd49ce3bf9219c0b1d4320`; 21 Python tests, nine sources / 934 bytes, documentation checks | +| #2241 | HTTP SSE first-delta, framing and buffered-compatibility tests | `c80a06411a235ee6ac33a39eb9b344fc877ce99d`; exact gate results tracked on its PR | +| #2775 | Isolate unit tests from the version-health HTTP request | `21e1ef2e4f0d3527e0790359b9b981411e818672`; focused checks/lint, typecheck/build, then 381 files / 6,153 tests passed / 3 skipped; PR #2810 | +| #2777 | Align frontend adapter/import/search and explicit PowerShell cwd instructions | `b42ce41e54aa8bb43533ce0834644664e01d2ee4`; doc links, docs/GitHub operations governance, diff, PowerShell parse and path checks | + +The representation and policy work are first contract slices. They do not create +a processing queue, runner, persistence facade, database migration, or runtime +authority. Their parent issues remain open. The benchmark does not run a +processor and has no audio/image/PDF quality, latency, WER or cost result. Missing +metrics are unavailable, not zero. Schema validation and persisted processor +identity limitations are tracked on #2319; no release-quality gate consumes the +initial fixture report. Live compatible-provider acceptance remains on #2241. + +All worker branches were created in isolated worktrees from pinned `origin/main` +and guarded before use. The six initial code/fixture slices use base +`db102dcba25cc5f347f22b38ce13d00502948ed9`; the instruction slice uses +`d65bd64c470a8a0fbc8e841d136aa7c089488eb0`. A later moving remote tip was not +substituted for those reviewed bases. Broad .NET/npm execution was serialized +after measuring about 2 GB free RAM on the 31.7 GB host; source review, small +checks and GitHub coordination continued concurrently. + +When free memory briefly rose above 7 GB, one frontend suite ran alongside the +single backend lane. Later pressure returned and the backend queue stayed serial. +The completed #2775 frontend run still printed 55 connection-error strings but +exited zero with no failed assertions. Its focused regression proves the default +version read makes no Axios call; the remaining console messages are not attributed +to that endpoint and a globally network-silent suite is not claimed. + +After the maintainer requested lower use of high-intelligence models, the Astra +and Terra threads stopped new work. Luna took over remaining execution and the +single combined CI monitor; a mechanical Spark task prepares the policy handoff. +The already-completed independent source reviews were retained without duplication. + +## Parked queue and finite budgets + +- #2790 remains parked at `cdfd28c31f3ec9da64989070ec6206c46316f02b` after its + review/fix ceiling. Confirmed HIGH receipt failure #2795, failed CI and conflicts + remain. This wave did not open a third repair round. +- #2797 remains parked at `869e592c260f85c1c87d82a86912600e914304ed`. The failing + browser test expects repeated-refusal feedback after changing boards and receiving + a second 403. The state reset removes that feedback; 179 passed, 12 skipped and + one failed. This is a confirmed non-blocking product finding on #2214, but failing + CI still prevents merge. No retry-to-green or severity inflation was used. +- #2769 has the narrow expected-version assertion fix at + `59f65034d15c811ea5530040309189e7b01e632f`. #2803 carries the coherent Vitest 5 + trio at `ef62babbc4ed2627d5867371ffb89f61f44a664a`; install and 47 focused tests + passed, with broader hosted results on the PR. Both remain subject to maintainer + control-path review. The three incompatible individual upgrades #2770/#2771/#2773 + remain open until the replacement is authorized and merged. +- #2791 (`c086e47b86ab5efbb0fd31fc56a640c33419a07f`) and #2792 + (`2c3eaa3b114635634cc98ac2d0eab3fc5925dcd8`) passed independent review and hosted + checks at these heads, but their maintainer control-plane review remains open. + +## Authority correction and human actions + +The coordinator merged #2772 without the maintainer's own review. This was an +error: `ci/policy.v1.json` explicitly includes `backend/Directory.Packages.props` +as a control path, so ADR-0066's amendment and the active lane contract required +that review in addition to green CI and independent review. Disclosure is on +[#2772](https://github.com/Chris0Jeky/Taskdeck/pull/2772#issuecomment-5577569078) +and [#2337](https://github.com/Chris0Jeky/Taskdeck/issues/2337#issuecomment-5577569315). +No retrospective approval, acknowledgement or rollback decision is inferred. +The same declaration includes frontend package manifests/locks; #2769 and #2803 +were corrected to the maintainer-review queue before any merge. + +[OUTSTANDING_TASKS.md](../../OUTSTANDING_TASKS.md) remains authoritative. Its new +unchecked September 8 checkpoint carries this error and the four current review +PRs. The earlier checked SC-10 row covered a named historical batch only. Existing +legal/publisher, signing, private-instance, cutover, release, credential and +subjective acceptance items remain open as recorded there. No deployment, +publication, account/settings change or real-data repair occurred in this wave. + +## Saved state and next action + +The primary checkout's unrelated `backend/.claude/` files and pre-existing worktrees +were preserved. The local coordinator ledger records exact execution receipts, +scoped project writes, evidence locations and cleanup results. Raw test outputs +and operational logs are kept outside Git. + +Refresh exact heads, bases, checks and unresolved threads before resuming a parked +PR. Preserve the spent review budgets. Continue the remaining acceptance on parent +issues rather than closing them for a first foundation slice. The broader #2235 +spring-cleaning, milestone reconciliation and release acceptance remain separate. From d09631be9ea9fef6606edd71862ce65ab497b776 Mon Sep 17 00:00:00 2001 From: Chris0Jeky Date: Tue, 8 Sep 2026 02:49:11 +0100 Subject: [PATCH 2/2] docs: save final verification and resume points --- .../2026-09-08-parallel-issue-wave.md | 38 ++++++++++++++++++- 1 file changed, 37 insertions(+), 1 deletion(-) diff --git a/docs/analysis/2026-09-08-parallel-issue-wave.md b/docs/analysis/2026-09-08-parallel-issue-wave.md index 072079ee5..91e8186dd 100644 --- a/docs/analysis/2026-09-08-parallel-issue-wave.md +++ b/docs/analysis/2026-09-08-parallel-issue-wave.md @@ -32,7 +32,7 @@ maintainer review is a separate failure of authority, not a failed test. | #2260 | CF06-1 immutable representation header, supersession edge and descriptor | `9fd6a69e257db7e91fbe40064767293e43901a86`; 21 Domain and 1 Application targeted checks, then full backend 8,995 passed / 5 existing skips; PR #2809 | | #2257 | CF03-1 immutable processing policy and canonical digest | `ad02598a038bb0a969c66919db66a91ba2f59907`; 12 focused tests and full backend exit 0; final per-project totals not captured; PR #2811 | | #2319 | Initial synthetic text corpus and per-kind scorer | `6c9bec284b1feaade2cd49ce3bf9219c0b1d4320`; 21 Python tests, nine sources / 934 bytes, documentation checks | -| #2241 | HTTP SSE first-delta, framing and buffered-compatibility tests | `c80a06411a235ee6ac33a39eb9b344fc877ce99d`; exact gate results tracked on its PR | +| #2241 | HTTP SSE first-delta, framing and buffered-compatibility tests | `d0ba6c9d9bf49d6c80f948aa560a26c0cba766f4`; 2 focused tests, then full backend 8,975 passed / 5 existing skips; PR #2812 | | #2775 | Isolate unit tests from the version-health HTTP request | `21e1ef2e4f0d3527e0790359b9b981411e818672`; focused checks/lint, typecheck/build, then 381 files / 6,153 tests passed / 3 skipped; PR #2810 | | #2777 | Align frontend adapter/import/search and explicit PowerShell cwd instructions | `b42ce41e54aa8bb43533ce0834644664e01d2ee4`; doc links, docs/GitHub operations governance, diff, PowerShell parse and path checks | @@ -84,6 +84,22 @@ The already-completed independent source reviews were retained without duplicati (`2c3eaa3b114635634cc98ac2d0eab3fc5925dcd8`) passed independent review and hosted checks at these heads, but their maintainer control-plane review remains open. +Open implementation PRs at wrap-up are #2809 (representation), #2810 (unit health +isolation), #2811 (policy snapshot) and #2812 (SSE tests). Required hosted jobs +were still running at the final REST checkpoint; #2812 was newly published. +No completed milestone or merge-ready claim is made from those partial CI results. +The two connector P2s on #2811 are replied to and tracked on #2257: persist the +canonical payload alongside its digest in CF03-2, and reject final-newline tokens +with absolute regex anchors. The latter was reproduced directly; no current runtime +dispatch or cost enforcement is wired to this contract. These are non-blocking +follow-ups, not an extra repair round. + +External PR #2807 remains owned by its overhaul thread and is excluded from this +wave's delivery count. Its model snapshot must retain #2805's repair column when +integrating the three overhaul migrations; the ordering and both documentation +records were called out on that PR. Its separate HIGH review fixes remain with +that author thread. + ## Authority correction and human actions The coordinator merged #2772 without the maintainer's own review. This was an @@ -110,6 +126,26 @@ were preserved. The local coordinator ledger records exact execution receipts, scoped project writes, evidence locations and cleanup results. Raw test outputs and operational logs are kept outside Git. +The curated local bundle is +`C:\Users\Public\codex-shell-home\taskdeck-wave-20260908`: copied test logs and +receipts, literal ignored-file inventories, normal worktree-removal records, and +the coordinator ledger. Source heads are pushed; only this wave's disposable +worktrees are removed. The CI monitor stopped at the maintainer's wrap-up request, +and the final SSE test process completed before handoff. Unrelated shared compiler, +application and external-overhaul processes were left alone. + +The SSE test head changed during local proving: a missing HTTP JSON import and a +payload-casing assumption needed two test-only commits. The final head above, +rather than the earlier reviewed `c80a06411`, owns the executed evidence. A narrow +Luna check supplements the original Terra review for those corrections. + +Forty previously missing issue Priority assignments were reconciled and verified +against Project values; 38 Project values changed and status fields were preserved. +The full-project audit did not produce a clean result: an earlier apply refused a +changed live plan before writes, and the final read-only run hit an API quota error. +Follow-up PR/comment reads used REST. The scoped 40-item verification is not a +complete-project audit; #2235 retains that remaining check. + Refresh exact heads, bases, checks and unresolved threads before resuming a parked PR. Preserve the spent review budgets. Continue the remaining acceptance on parent issues rather than closing them for a first foundation slice. The broader #2235