feat(maint): upstream-replayable distribution model (immutable base, sync tool, self-update policy) #197
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nsaspy/a0-symbolics!197
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/upstream-replayable-model"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Makes a0-symbolics an upstream-replayable Agent Zero distribution instead of a conventional long-lived fork, per the maintenance-model redesign.
maint/upstream.tomlpins the immutable upstream v2.10 base commit and the Symbolics distribution remotes; release identity isa0s-v<upstream-tag>.<series>resolved byhelpers/symbolics_release.helpers/self_update.pyand the durable updater now resolve update sources from the Symbolics distribution only; raw upstream sources and marker-less targets are refused;a0s-release tags replace bare upstream tags (WebUI + tests updated).scripts/upstream-sync:status/plan/prepare/resume/verify/fork-surface— deterministic, isolated-worktree replays with rerere, range-diff, and machine reports.plugins/_a0s_promptscarries the Symbolics prompt deltas so upstream prompt files stay unmodified (fork surface shrinks).b1cbd1f9) in an isolated worktree; 11 conflict stops resolved deliberately (tool_choice retry vs upstream transport rewrite, XML tool-call extraction vs upstream fast-fail guard, Responses-first default preserved); verify gate green (147 pytest, import/plugin/prolog smoke, docker compose, nix flake metadata, live/api/healthboot). Evidence inmaint/reports/prepare-v2.12/.maint/AGENTS.md(new), root + scripts contracts,docs/guides/upstream-sync.md.Verification
prolog-verify check: passed (machine-recorded observations).maint/fork-surface.toml.maint/upstream.tomlstill records v2.10 as the distributed base; bumping to the replayed v2.12 head is the upgrade-PR decision this prepares.