Phase 0 (M0): hard split, private registry, publish guards, Effect baseline

Branch phase0/hard-split-registry-guards → staging. 17 commits (git log --oneline origin/staging..HEAD), executing roadmap Phase 0 (docs/specs/platform-gaps/50-roadmap-workpackages.md §5): WP-RN-01, WP-RN-02, WP-RN-03, WP-RN-04, WP-RN-08 (spec 15) and WP-T3-32 stage 1 (spec 10), plus the owner-decided scope re-lock @agentfabric → @fabricstack.

Invariants held throughout and re-verified at review time (2026-09-28): the public repository a5c-ai/babysitter was never written to (gh api repos/a5c-ai/babysitter --jq .pushed_at → 2026-09-16T19:59:50Z, unchanged since before cutover; the upstream remote's push URL is no_push); nothing was published to registry.npmjs.org (@fabricstack/smoke → HTTP 404 there); the only registry write is the throwaway smoke package in Artifact Registry.

Per-WP summary

M0 exit criteria (roadmap §5, Phase 0)

WP acceptance criteria not fully closable inside this branch (accepted by design; listed, not hidden)

• **WP-RN-01 AC1(b)** — the ≥7-day passive propagation watch is only **started** (2026-09-28T07:29:35Z): cutover recorded, scheduled read-only watch installed, first runs green. The roadmap's wall-clock note keeps this off Phase 1's critical path; only the formal M0 gate record waits for the window (it must also contain at least one post-cutover public commit, and the public repo has not moved since 2026-09-16).
• **WP-RN-02 AC3 / test requirement "rehearsal PR merged"** — PR #2 (intake/76434c2, label upstream-intake, path map recorded) is **open, not merged**; merging is the owner's decision.
• **WP-RN-04 G1 selector switch** (spec 15 §4.3: "must change in the same commit" as the manifests are pinned) — no manifest is renamed yet, so the switch is implemented behind FABRIC_PRIVATE_TRAIN=1 (default off, byte-identical to the old inventory: 43 @a5c-ai/* entries, pinned by test) and flips in the RN-1 train (WP-RN-05/07). G2(b), G2(d), the G5 legacy-collision tolerance and the whole-tree npmjs rules follow the same flag.
• **WP-RN-04 G4** — npmjs organization fabricstack is **not yet created** (pending owner action; the scope is free as of 2026-09-28, probe --g4-status → unregistered).
• **WP-RN-04 G3 at organization level** — org secret NPM_TOKEN still has visibility all (readable by this repo through two inherited legacy @a5c-ai train workflows, reported by the guard as 8 legacy-train notices); restriction is a pending owner UI action.
• **WP-RN-08 AC3** (first real landed fork passes the gate un-waived) — not yet exercisable; no fork has landed. Owned by WP-T3-01/02 (M2 exit criterion 1).
• **WP-T3-32 AC3–AC5** (stage 2: build matrix, Vite/vitest re-platform, engine floors) — out of scope by the roadmap's staging; deferred in docs/EFFECT-BASELINE.md §7.

Pending owner actions (outside the repository)

1. **G4 — register the fabricstack org on npmjs** per g4-npmjs-org-runbook.md: company account, publish nothing, 2FA required, sole owner; then record the org URL in publish-guards.md (G4 row). Verify with node scripts/ci/publish-isolation-guard.cjs --g4-status → registered-no-packages. 2. **G3 — restrict org secret NPM_TOKEN** to selected repositories excluding a5c-ai/fabric (GitHub UI; the API path needs the secret value) per g3-npm-token-restriction.md. Verify: gh api orgs/a5c-ai/actions/secrets/NPM_TOKEN --jq .visibility → selected. 3. **Close the ≥7-day propagation watch** once the window has elapsed and contains a post-cutover public commit: record the last green run, the git for-each-ref after-snapshot and the ref-by-ref diff against fabric-refs-baseline.txt in watch-baseline.md ("Closing procedure"). Until the workflow is on main, the schedule does not fire; dispatch with gh workflow run upstream-propagation-watch.yml -R a5c-ai/fabric --ref <branch>. 4. **Decide PR #2** (merge or close the intake rehearsal). 5. Optional cleanup: delete the old-scope @agentfabric/smoke@0.0.0-smoke.2 from fabric-npm (gcloud artifacts packages delete @agentfabric/smoke --repository=fabric-npm --location=us-central1 --project=boot-464019 --quiet) and update the AR repository description (still "agentfabric private npm packages (fabric)").

Deferred items

• **G1 selector switch** to publishConfig.registry-keyed selection: RN-1 train (WP-RN-05/07), behind FABRIC_PRIVATE_TRAIN.
• **WP-T3-32 stage 2**: apps re-platform on stock Vite/vitest/tsc (@voidzero-dev/* grep gate), workspace engines ≥22.16 with the sub-floor CI run, tracked-fork build matrix; depends on WP-T3-01. Stage-2 input recorded: @effect/vitest@4.0.0-rc.115 peers on vitest >=5 <6 while fabric runs 4.1.6, so it is pinned and locked but not yet usable as a harness.
• **@effect/vitest upstream patch dropped (DROPPED-toolchain)**, not ported: its only effect is vitest → vite-plus/test import rewriting, which is wrong under stock vitest; test 10 pins the unpatched imports. The WP objective text says "patched @effect/vitest"; the ACs (1), (2), (6) do not require it and the decision is recorded in docs/EFFECT-BASELINE.md §3.
• **Patch inventory count**: 17 mobile-only (not the 19 the WP brief assumed) because @legendapp/list and @pierre/diffs are also consumed by t3:apps/web; those two plus @ff-labs/fff-node and dbus-next are DEFERRED-stage-2 to the WPs that land their consumers.
• **Retargeting the 43 @a5c-ai manifests and the release workflows** (WP-RN-05/06/07); the two legacy workflows referencing secrets.NPM_TOKEN become hard findings under --private-train.

Review observations (not failures)

• git grep -l "@agentfabric/" lists four files: the two historical records (g4-npmjs-org-runbook.md, scope-relock.md) and two WP-RN-08 negative fixtures (scripts/ci/fixtures/no-double-rename/negative/rejected-scope/packages/x/package.json, scripts/ci/fixtures/no-double-rename/spec10/negative.md) that deliberately use the rejected scope to prove the foreign-scope-new-unit / rejected-scope-name rules trip. scope-relock.md's "only two files" statement predates those fixtures.
• ci.yml triggers on pull_request and workflow_dispatch only, so the publish-isolation job (WP-RN-04/08) and the test job's "Effect baseline" step have not yet executed in GitHub Actions; this PR's CI run is their first. The one ci.yml run tied to this branch (PR #2, run 36395354707) ran the public-push-guard job green; its four red jobs (Gateway Node engine floor ×2 at "Build adapters gateway", Lint, Tests, Package at "Release tooling tests", Docs QA at "Docs quality gates") fail on exactly the same steps in the pre-Phase-0 run 36332996215 (c0dd9722c, PR #1) and are unrelated to this branch.
• npx markdownlint-cli2 docs/specs/platform-gaps/phase0/watch-baseline.md reports MD010 hard tabs at lines 385–386 (inside the verbatim git ls-remote dump). The repo's markdownlint scope (.markdownlint-cli2.mjs globs) does not include the phase0 records; root npx markdownlint-cli2 → 0 errors.

How to verify

Run from the repository root on this branch (node_modules installed with npm install --legacy-peer-deps).

# Guards: self-tests (fixtures red, tree green)
node scripts/ci/public-push-guard.cjs --self-test
node scripts/ci/publish-isolation-guard.cjs --self-test
node scripts/ci/no-double-rename.cjs --self-test
node scripts/ci/check-spec10-names.cjs --self-test

# Guards: node:test suites
npm run test:public-push-guard
npm run test:publish-guards
npm run test:binary-renames
npm run test:no-double-rename
npm run test:effect-baseline

# Negative fixtures trip (each exits 1)
node scripts/ci/public-push-guard.cjs scripts/ci/fixtures/public-push-guard/negative/git-push-https.workflow.yml
node scripts/ci/publish-isolation-guard.cjs --root scripts/ci/fixtures/publish-guards/g1/negative/public-npmjs
node scripts/ci/publish-isolation-guard.cjs --root scripts/ci/fixtures/publish-guards/g2/negative/npmjs-publish-private-scope
node scripts/ci/publish-isolation-guard.cjs --root scripts/ci/fixtures/publish-guards/g3/negative/npmrc-token
node scripts/ci/bin-collision-guard.cjs --root scripts/ci/fixtures/publish-guards/g5/negative/duplicate-bin
node scripts/verify-release-artifacts.mjs --package-dir scripts/ci/fixtures/publish-guards/g6/negative/private-scope-npmjs --skip-build --report-dir "$TMPDIR/g6"
node scripts/ci/no-double-rename.cjs --root scripts/ci/fixtures/no-double-rename/negative/t3code-scope

# Effect singleton
npm ls effect --all

# Scope constant, routing, credentials
node -e "console.log(require('./package.json').fabric)"
grep "@fabricstack:registry=" .npmrc
grep -iE "_authToken|password|token=" .npmrc            # must print nothing (exit 1)
git log --all -p -- .npmrc | grep -iE "_authToken|password|token="   # must print nothing

# Artifact Registry (needs gcloud auth as a reader of fabric-npm)
npx -y google-artifactregistry-auth --repo-config=.npmrc --credential-config="$HOME/.npmrc"
npm ping --registry https://us-central1-npm.pkg.dev/boot-464019/fabric-npm/
npm view @fabricstack/smoke versions --registry https://us-central1-npm.pkg.dev/boot-464019/fabric-npm/
node scripts/ci/publish-isolation-guard.cjs --g4-status   # informational: unregistered until G4 is done

# Hard split invariants (read-only)
git remote -v                                             # upstream ... no_push (push)
bash scripts/ci/upstream-propagation-watch.sh             # verdict: PASS
gh api repos/a5c-ai/babysitter --jq .pushed_at            # 2026-09-16T19:59:50Z
gh api repos/a5c-ai/fabric/rulesets                       # id 24103129 active
gh pr view 2 -R a5c-ai/fabric --json state,labels
gh run list -R a5c-ai/fabric --workflow ar-smoke.yml --branch phase0/hard-split-registry-guards --limit 3
gh run list -R a5c-ai/fabric --workflow upstream-propagation-watch.yml --branch phase0/hard-split-registry-guards --limit 3

🤖 Generated with Claude Code