1.8 KiB
#1500 fixture-only increment publication
Reviewed source commit: 3daee5ad89, pushed to origin/refactor and exact remote pin verified. All21 files in independently approved manifest11255dd4 match committed bytes. Ten changed files selectively committed; unrelated agent/WUI/skill artifacts remain unstaged.
Clean committed archive verification, with isolated HOME/environment and a disposable Git baseline for conductor tests:
- Package and launcher: 74/74, /tmp/m20-committed-package-launcher.log.
- Config: 24/24, /tmp/m20-committed-config.log.
- Auth: 15/15, /tmp/m20-committed-auth.log.
- Foundation: 43/43, /tmp/m20-committed-foundation.log.
- Conductor: 17/17, /tmp/m20-committed-conductor.log.
Task/release suites were not run and are not claimed passing. Jason explicitly approved this increment-specific applicability disposition, recorded in 2026-09-10_m20-publication-owner-disposition.md. That record also tracks the separate headless identity-environment fix intake. Earlier failed evidence remains preserved.
Owner demonstration
From repository root:
node --test --test-name-pattern='two concurrent|expired credentials refresh' packages/mosaic/tests/materialize.test.mjs
Expected: two passing tests. They demonstrate two executions of the same agent selecting separate fixture accounts with distinct private outputs, and expired synthetic OAuth rotating before generation with reuse in the next execution. Tests remove temporary state. They print test results, not credential contents. No real Pi, OAuth, network clients or services run.
Implementation and independent review are complete; owner fixture-demo acceptance remains pending. #1500 should not be called owner-accepted before that response. Production credentials, refresh services, launcher integration and deployment remain outside this increment.