Repository navigation
docs(BACKEND_GUIDE): refresh version banner + msb differences/limitations table (parity gaps B/C/D/I) #227
Description
Summary
docs/BACKEND_GUIDE.md drifted from shipped behavior. The bulk was refreshed on
the parity branch (PR #233): the stale "1.2.0" banner and per-backend version
columns are gone, and the "Differences from sbx" + "Known limitations (msb)"
sections now cover the current gaps. This issue stays open for the follow-through
as the remaining gaps land.
This is gap J in the sbx↔msb backend parity epic (#234).
Remaining follow-through
- Flip the "Differences from sbx" table + msb capability-flags from "scheduled"
to "shipped" as the underlying gaps land:- B — snapshots (flag drop to 0 / eventual
acq snapshot, acq(msb): drop unreachable SUPPORTS_SNAPSHOTS flag to 0; wire acq snapshot as follow-up #225). - C — msb secret binding breadth (generic custom endpoints, acq(msb): bind generic custom-endpoint secrets at provision (not just usai) #226).
- A — neutral port-publish/background once acq: implement neutral port-publish + background kit vocabulary (ADR-0013) and msb consumer #224 lands (ADR-0014).
- B — snapshots (flag drop to 0 / eventual
- Keep the
scripts/verify-backendsmanual cadence note current (gap I): run
on a KVM-capable host after each release / after ≥3 behavior-affecting fixes
(AGENTS.md §8.3), since it cannot run in CI. - Bump
last_updatedon each pass.
Already done (on the parity branch)
- Version banner delinked from 1.2.0 (now the 2.x line); per-backend version
columns dropped. - Differences table + limitations cover snapshots (B), secret table (C),
the removedopencode-web.sh(now theopenchamberkit; gap D), and the
verify-backends cadence (I). - Secret section + capability flags reflect the github-via-REST binding (fix(msb): install/launch the agent + mount workspaces at their host path #230).
Related
- Part of Epic: sbx↔msb backend parity #234 (sbx↔msb backend parity epic — gap J)
- acq: implement neutral port-publish + background kit vocabulary (ADR-0013) and msb consumer #224 (gap A), acq(msb): drop unreachable SUPPORTS_SNAPSHOTS flag to 0; wire acq snapshot as follow-up #225 (gap B), acq(msb): bind generic custom-endpoint secrets at provision (not just usai) #226 (gap C)
AI-assisted (OpenCode); requires human review.
Activity
fix(msb): install/launch the agent + mount workspaces at their host p…
mogul commentedon Jul 29, 2026
Partially addressed on this branch (the post-rebase parity-docs pass):
docs/BACKEND_GUIDE.mdhas been refreshed —acqdoesn't surface it; flag slated to drop to 0, acq(msb): drop unreachable SUPPORTS_SNAPSHOTS flag to 0; wire acq snapshot as follow-up #225), gap C (secret binding is a fixedusai+githubtable; arbitrary custom endpoints stored-but-not-bound, acq(msb): bind generic custom-endpoint secrets at provision (not just usai) #226), the agent-install-on-plain-base behavior (fix(msb): install/launch the agent + mount workspaces at their host path #230), and gap D (opencode-web.shsbx-only; openchamber supersedes, patterns feat(acq)!: sbx↔msb backend parity, incl. live openchamber-on-msb (omnibus #234) #233).scripts/verify-backendsmanual cadence (KVM host, after each release / ≥3 behavior-affecting fixes, per AGENTS.md §8.3).[email protected]) from fix(msb): install/launch the agent + mount workspaces at their host path #230; msb flag shapes now cited against 0.6.7.last_updatedbumped;related_filesgains ADR-0014 + the parity map.Keeping this open: the guide currently describes gaps A–C as scheduled, not done. As #224/#225/#226 actually land, the differences table + capability flags need a final pass to flip them to shipped. Also note ADR-0014 is the renumbered companion (was 0013 before #229's per-sandbox-token ADR-0013 merged).
AI-assisted (OpenCode).
feat(acq)!: sbx↔msb backend parity, incl. live openchamber-on-msb (om…