Files
stack/docs/plans/reviews/2026-09-12_m20-increment2-owner-acceptance.md
T
jason.woltjeandClaude Fable 5.1 1993039c76 Record owner acceptance and closure of #1500 fixture increment
Jason reran the two-test fixture demonstration on the canonical checkout
at 5abbabb7 (2/2 pass). Records-only: acceptance receipt, BUILD-LOG,
SESSIONS and CURRENT.md next action (MVP re-plan). No source change.

Co-Authored-By: Claude Fable 5.1 <[email protected]>
2026-09-12 06:47:24 -05:00

52 lines
2.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# #1500 fixture-only increment: owner acceptance
Date: 2026-09-12. Recorded by jarvis (Claude Code), owner-directed takeover of the
darkwing pi session `01a07cfa-2c52-72c2-be4e-c80537b2d495`.
## What Jason ran
From the canonical checkout, in a shell re-pointed at `/mnt/storage/src/mosaic-stack`:
```
$ git rev-parse --short HEAD
5abbabb7
$ node --test --test-name-pattern='two concurrent|expired credentials refresh' packages/mosaic/tests/materialize.test.mjs
✔ two concurrent workspaces of the same agent publish distinct complete private generations (72.611768ms)
✔ expired credentials refresh under transaction and subsequent generation reuses rotation (93.302206ms)
tests 2 pass 2 fail 0 cancelled 0 skipped 0 todo 0
```
Jason pasted this output as his response to the demonstration request recorded in
`2026-09-10_m20-increment2-publication.md`. The coordinator reran the same command
on the same commit earlier the same day with the same 2/2 result.
## Acceptance ruling and assumption
The publication record asked for "owner fixture-demo acceptance" as the last gate
before closing #1500. Jason's own passing run on the exact published commit is
taken as that acceptance. Assumption stated: the pasted output, without an
additional word of approval, is the acceptance response; if Jason intended only to
report the result, #1500 can be reopened without loss.
## What this accepts and what it does not
Accepted: the fixture-only increment at source `3daee5ad89dc6a006ca554ad7fda2b23eb96bb03`
(records `5abbabb74b4f354481626f01e837d5fa23d59da9`), independently approved by Filbert
at manifest `11255dd4`, with the owner's earlier task/release not-applicable disposition
(`2026-09-10_m20-publication-owner-disposition.md`).
Not accepted or authorized by this record: production credential refresh, real Pi or
OAuth use, launcher integration, services, Docker release, deployment, or any
increment 3. The headless identity-environment leak remains a separate intake with
Darkwing as owner. Task/release suites were not run for this increment.
## Why the first demo attempt failed
The 2026-09-11 attempt reported the test file missing and HEAD `5d277000`. Cause:
the terminal was a bash started 2026-09-07 14:26 UTC, before the repository
conversion cutover; its working directory followed the moved v1 tree into the
retired rollback copy while `pwd` kept printing the canonical path. A `git pull`
in that shell on 2026-09-12 fast-forwarded the retired copy to `next` at
`2101c9b4` (fred, #1502); the copy is clean and `before-v1` remains at `5d277000`.
No canonical-checkout change was involved.