the-custodian/docs/changes/netkingdom-target-2026-10-18/wp80-workplan-refinement-r1/README.md

42 lines
2.6 KiB
Markdown

# WP-80 progress visibility and task refinement
The user requested smaller tasks and a transparent account of delivered work.
The active workplan now starts with source/integration/native progress, Now/Next,
publication limits and an explicit update rule. All six original task blocks,
statuses and UUIDs are preserved. The complete former 1,467-line file is retained
byte-for-byte in `workplan-before-refinement.txt`; the current file is much shorter.
T07-T40 are 34 Custodian evidence checkpoints linked to existing owner work:
seven completed source reviews, one native preparation in progress, 26 pending.
Each pending checkpoint names its owner and completion test. This exposes existing
delivered work and the actual remaining integration, build, runtime, lifecycle,
recovery, audit and consumer acceptance. It creates no replacement owner backlog.
All 16 target gates and G01-G13 have explicit checkpoint mappings; all 116 original
ledger entries remain unchanged. No complete native gate is closed. The source
review counts are not an overall completion percentage. Active delivery work is
limited to two checkpoints, with one clear current item and a short next sequence.
The gap register now reflects accepted MFA preview/help corrections, delivered
sandbox and signing/verification source, actual current-token/Forgejo/database
proof and the new scanner source correction. Remaining native acceptance stays
explicit. The detailed implementation history links to the current workplan.
Normal Repo Manager assigned exactly 34 new canonical task bindings and changed
no old binding. Its actual workplan parser verifies 40 tasks, unique bindings,
9 done / 4 progress / 27 todo across both umbrella and delivery records, all local
links, and an acyclic internal dependency graph. The delivery subset is 7 done /
1 progress / 26 todo. Source and native scopes remain distinct.
The first ordinary consistency run completed with zero failures/automation errors,
but publication was refused and C-17 skipped task writes because commits remain
unpushed. API readback still has the original six tasks. The new source records
await the normal projection after scanner correction; no API task creation bypass
is used. Existing source/CLI failure receipts are retained. The eight preexisting
worktree/index states remain preserved.
Decision: `77f88913-e893-42c8-992d-2f67df0a13db`, a Codex planning/reporting
decision implementing the user's request. It grants no runtime authority, owner
assent, residual promotion or changed security requirement. Evidence is in
`identifier-assignment.json`, `refinement-scope.json`, `validation.json`,
`consistency.json` and the projection readback receipt.