~bigbes/sr-ht-spec · events

c7t5jjqjt2c3udqemuijhp770288ui9k · 11 rows

idissue_idevent_typeactorold_valuenew_valuecommentcreated_at
019f8d29-5397-7e0d-b817-f81fc1ea0840spec-ejqcreatedEugene BlikhNULL2026-07-23T07:08:43Z
019f8d29-8cc1-7d90-b19d-8c7c5c36b37cspec-zqbcreatedEugene BlikhNULL2026-07-23T07:08:58Z
019f8d29-f61c-7c87-aa9f-c2d08aa053despec-3vzcreatedEugene BlikhNULL2026-07-23T07:09:25Z
019f8d29-fb60-73a1-be7f-c0199fcc676aspec-by6createdEugene BlikhNULL2026-07-23T07:09:26Z
019f8d2a-5ea5-7e9e-aab2-44c0ca2eb3c7spec-wcrcreatedEugene BlikhNULL2026-07-23T07:09:52Z
019f8d2a-626d-73e4-9e8d-d0df4ddd8437spec-ar4createdEugene BlikhNULL2026-07-23T07:09:53Z
019f8d2a-66d9-73c8-b102-455f9cb41611spec-43wcreatedEugene BlikhNULL2026-07-23T07:09:54Z
019f8d51-a40a-7cec-9ccc-53dcd00c9666spec-43wclosedEugene BlikhStale apk pins already bumped in the stack versions.env (paste 0.19.4-r0, hub 0.31.1-r0); fixed out of band.NULL2026-07-23T07:52:45Z
019f8d51-d807-7465-87f6-e94b035bd584spec-zqbclaimedEugene Blikh{"id":"spec-zqb","title":"Phase 3: write plane — agents propose","description":"The agent half of the loop, and the service's whole premise: an agent proposes a document change, gets back a link, a human approves in a browser. Until this ships, agents can only read.","design":"Scope: proposals (branch proposals/\u003cid\u003e + Postgres row, state open-\u003emerged|rejected); the If-Match tree-splice merge with the four staleness cases and the ancestry check gitx flagged; the single agent token + mandatory provenance trailers; spec_propose / spec_comment over REST + MCP; every write response returns {proposal, url} so the agent can hand over a link. Prereqs found during Phases 1-2: (1) service.ListProposals(space, state) — graph proposal listing is stubbed and db only has ListProposalsByState; (2) IsAncestor(proposalHead, H) check before Merge so an already-merged proposal reports 'already merged' not a confusing 409; (3) auto-merge policy evaluation (.spec.yml AutoMerges) which the reconciler's 'approval=policy' inference also wants. Dispatch like Phases 1-2: proposal orchestration in service/ first and committed, then surface tools fan out. This is where the merge model and reconciler first run under real proposals rather than on paper.","status":"open","priority":1,"issue_type":"feature","owner":"bigbes@gmail.com","created_at":"2026-07-23T04:08:58Z","created_by":"Eugene Blikh","updated_at":"2026-07-23T04:08:58Z"}{"assignee":"Eugene Blikh","status":"in_progress"}NULL2026-07-23T07:52:59Z
019f8d73-0a9b-7e86-8f51-1851559c98a1spec-jjocreatedEugene BlikhNULL2026-07-23T08:29:14Z
019f8d73-443d-74e2-b383-b1fe9cac3f89spec-zqbclosedEugene BlikhWrite plane shipped: service.Propose/Merge/Reject/ListProposals with provenance trailers, auto-merge policy, If-Match staleness + already-merged ancestry check; surfaces graph (Proposals port), mcpsrv spec_propose, and new api/ REST PUT — every write returns {proposal, url}. Validated end-to-end against Postgres. spec_comment deliberately deferred to Phase 5 (spec-by6), which gates the comment schema on the Phase 4 review UI; the approve/reject browser UI is Phase 4 (spec-3vz).NULL2026-07-23T08:29:29Z