Stand up the Intent Solutions fork infrastructure for the Buzz adoption

[jeremylongshore]

Cluster issue for Phase 1 / E1 of the Buzz adoption master blueprint
(000-docs/001-PP-PLAN-buzz-adoption-master-blueprint.md): fork + clone +
beads/Dolt activation, master blueprint + decision record + deploy-posture
doc + FORK.md (all additive-only — zero upstream-path edits), testing-SOP
baseline (TEST_AUDIT.md), three-way mirror (this issue + Plane BUZZ),
and memory seeding.

Beads: buzz-4ei (epic) + children buzz-4ei.1–buzz-4ei.4
Plane: BUZZ (epic issue linked after bd-sync)

Operator-private detail for the wider adoption (hosting, keys, member data)
lives in the private operations repo — not here.

• Jeremy Longshore
  intentsolutions.io

[jeremylongshore]

Linked bead: spine-8fl (source of truth). Use bd-sync to mirror updates.

[jeremylongshore]

Linked bead: buzz-4ei (source of truth). Use bd-sync to mirror updates.

[jeremylongshore]

bd-sync from buzz-4ei: E1 milestone: blueprint set + FORK.md + TEST_AUDIT.md authored (buzz-4ei.1, .2 closed); beads write-path root-caused (bd contributor-role fork routing) and fixed via --role maintainer; PR opening next. Note: epic was re-minted from buzz-ekg to buzz-4ei during the store rebuild.

[jeremylongshore]

bd-sync from buzz-4ei: E1 shipped: PR #2 squash-merged to fork main (6cf4df9) after CodeRabbit review (4 findings fixed in e49ed40, 2 declined with reasons). Children .1/.2/.4 closed with evidence; .3 (fork-lane test layers) remains open — epic stays in_progress until it lands. Deferred: epic-boundary Dolt tag until dolt-mcp-vcs is available (system dolt CLI is version-skewed vs bd's embedded engine).

[jeremylongshore]

bd-sync from spine-8fl: Phase 1 complete on the fork side: #2 merged (blueprint/decision-record/deploy-posture/FORK.md/TEST_AUDIT + beads prefix buzz, epic buzz-4ei — .1/.2/.4 closed, .3 open); Plane project BUZZ live; ops/buzz lane + changelog on intent-os PR block#274 (awaiting CI). Phase 2 hosting NOT started; gates blocking; nothing before Friday MX cutover.

[jeremylongshore]

bd-sync from spine-8fl: Estate-side Phase 1 settled: intent-os PR block#274 MERGED (ops/buzz lane + changelog + estate-CI executor). Merge rode the estate-owned CI lane: Actions dispatch is billing-blocked, so ops/ci-runner/estate-ci-validate.sh ran the exact ruleset gates on the dev box (gates 137s / drills 214s / gitleaks clean) and posted the required contexts via the status API; review rule satisfied via the ruleset's configured repo-admin bypass (same lane as PRs 272/273). Actions workflows temporarily disabled until org billing is fixed.

[jeremylongshore]

bd-sync close on buzz-4ei: E1 complete: all 4 children closed with evidence (PRs #2/#3/#5/#6 merged; blueprint ledger E1=COMPLETE; GH cluster #1 auto-closed by PR #6). Fork contract now machine-enforced. Phase 2 hosting opens per blueprint after the MX cutover. (GH issue left open — covers other beads)