From 831d15f0b42a2eba899375e9b06a145345747e64 Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Tue, 3 Nov 2026 17:01:26 -0600 Subject: [PATCH] docs: prepare lifecycle execution and original request evidence (#1839) --- BUILD-LOG.md | 2 ++ docs/SESSIONS.md | 1 + .../2026-11-03_request-lifecycle-implementation.md | 10 +++++++++- 3 files changed, 12 insertions(+), 1 deletion(-) diff --git a/BUILD-LOG.md b/BUILD-LOG.md index fccb886d0..e6626900d 100644 --- a/BUILD-LOG.md +++ b/BUILD-LOG.md @@ -5983,3 +5983,5 @@ Owner directed static-only fallback after actual nativepriority drift: no new pr 2026-11-03 | Lead Codex, terminology migration discovery (#798, Gitea #1840) | Before: user-facing prose, role contracts, owner principal, config human key and events/transports use legacy human terminology; a separate user principal already means a granted user. Jason explicitly includes internal identifiers in the enhancement. Created #798 and #1840; Luna will inventory a compatible staged rename after #797, with no change to authority or immutable historical evidence. 2026-11-03 | Lead Codex, #798 / Gitea #1840 inventory outcome | Luna read-only report completed with compatibility concerns. Lead verified owner-vs-granted-user principal split, business config key, optional restricted role messaging and human.input schema/trigger; recorded corrected scope and staged migration in docs/plans/2026-11-03_user-terminology-migration.md. No runtime/code/config rename performed. Implementation follows #797; stronger GPT review required for schema/proof/history readers. Queue refusal in linked inventory checkout was not bypassed. + +2026-11-03 | Lead Codex, #797 / Gitea #1839 lifecycle plan integration | Integrated Astra planning commits as 260f2ce7e and 63bd48a5f; eight bounded implementation tasks and proposed exact PRD addendum, no production code. Lead checked project-map/runtime/requirement/continuation interfaces and retained the exact PRD adoption gate. Preserved the original pomodoro wording and owner-reported event/message IDs from the original conversation item as an explicitly labeled quotation export, not a raw runtime row/live receipt. Console implementation remains a separate active task; lifecycle implementation follows its review/integration. diff --git a/docs/SESSIONS.md b/docs/SESSIONS.md index 7bb2aa54c..87d6d109e 100644 --- a/docs/SESSIONS.md +++ b/docs/SESSIONS.md @@ -1983,3 +1983,4 @@ are never rewritten or removed; corrections are new entries. 2026-11-03 | Lead Codex GPT-6.1 Sol | Owner terminology enhancement (#798, Gitea #1840) | Created task covering user-facing prose and internal identifiers; compatibility inventory precedes implementation, owner-versus-granted-user authority preserved; lower priority than #797, active delegates steered to use user prose without overlapping a bulk migration. 2026-11-03 | Lead Codex correction to preceding #798 entry | The two #797 steer attempts were refused because both delegates were interrupted, not running; no steering was delivered. Read back both threads: Console baseline and failing tests exist; lifecycle investigation exists; no final reports. Resume the same checkouts with the terminology instruction, preserving progress. 2026-11-03 | Luna inventory, outcome recorded by lead Codex | #798 / Gitea #1840 user terminology including internal identifiers | Read-only report complete; lead verified consequential identity/config/event boundaries and recorded staged compatibility plan; linked-checkout queue refusal reported, no queue/source/host changes; enhancement remains open for implementation after #797. +2026-11-03 | GPT Astra lifecycle planner, integration by lead Codex | #797 / Gitea #1839 stages 2–4 | Two planning artifacts integrated; scoped requirements, protected bootstrap, guided/autonomous/attach, durable continuation and reviewed local HTML route specified; original-wording provenance supplied by lead; no source implementation/live acceptance/PRD approval claimed. diff --git a/docs/plans/2026-11-03_request-lifecycle-implementation.md b/docs/plans/2026-11-03_request-lifecycle-implementation.md index 6c291c159..f1b184ae5 100644 --- a/docs/plans/2026-11-03_request-lifecycle-implementation.md +++ b/docs/plans/2026-11-03_request-lifecycle-implementation.md @@ -30,7 +30,7 @@ A resource plan displays the source project/commit, upstream and existing fork s - No protected push, remote publication, merge, deployment, external message or spend is needed to deliver the reviewed local HTML. Such later actions keep their existing gates. - Effects reserve an operation key before execution; a retry reconciles evidence. Append corrections and supersessions; never rewrite run records, events, decisions, prior snapshots or receipts. - Managed product paths are under the configured `dataRoot`; reject links, overlaps, collisions and unrelated partial contents. Existing projects keep their paths. No new repository-root files. -- This assignment changes only its two planning artifacts. No queue movement, tracker writes, session/build-log edits, production setup or authority edits. Those explicit assignment limits supersede the general session protocol for this planning checkout. +- The original planning assignment changed only its two planning artifacts. A later execution assignment authorizes only the named task and its checks; it does not authorize production setup or unrelated authority edits. The controller records integration and session evidence centrally. ## Review focus @@ -253,3 +253,11 @@ Missing model account/route, PM/CTO/reviewer role, tracker sync credential or in Implement in Task order except that Task 3 may follow Task 4 while waiting for Stage 1 integration. Tasks 4/5 share the catalog contract; integrate together before enabling product task creation. Keep the feature unavailable until bootstrap admission, scoped validation and typed continuations all exist; no prompt-only partial release. The shortest end-to-end milestone is one product, one scoped task, one code commit/review and one downloaded HTML artifact. Multiple products share the same machinery; reusable mandates, automatic external project provisioning and broader artifact types are deferred. The checked-in design names the original pomodoro request but does not preserve its verbatim text/source event. The lead must supply a read-only export of that source for the final acceptance fixture; do not relabel a reconstructed prompt as the original. Fixture development can use an explicitly labeled representative request meanwhile. No other builder choice requires a fresh owner decision: source project and board are selected from actual configured resources in the displayed initial plan. Exact PRD amendment adoption remains a separate versioned approval record; this document is not that record. + +Lead provenance update, 2026-11-03: the owner's original incident quotation is +preserved at `/mnt/storage/scratch/tmp/mosaic-797-original-request-provenance.json`. +It contains the exact pomodoro wording, the original input/message IDs reported +by the owner, a SHA-256 of the wording and the source conversation item. Use it +for the original-wording acceptance fixture and preserve its provenance fields. +It is an owner-supplied quotation, not an exported runtime database row or live +acceptance evidence. Fixture and later live-run reports must keep that distinction.