Atomicity for local-fs write paths other than comment posting (issue creation, body edits) #27

New issue

Open

opened 2026-08-13 08:18:01 +00:00 by jbr870 · 0 comments

jbr870 commented

2026-08-13 08:18:01 +00:00

Owner

Spawned from finding F-PO-26-2-5 (out-of-scope) on issue #26 during decision D-PO-26-2-5.

Original scope note: Flagged as out of scope in the approved PREQ. Known follow-up candidate if the same pattern is observed on those paths — a sibling issue keeps it visible.

Disposition rationale: Issue creation, body edits, meta.json and seqfile updates still write directly to their final visible paths, so the crash-visibility class this feature closes for comments remains open there — lower blast radius (no cross-record identity collision), but the PREQ itself names it a known follow-up candidate. A sibling issue keeps it visible in the backlog instead of evaporating when #26 closes.

This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run /requirements --issue={new-number} to flesh it out before planning.

Spawned from finding `F-PO-26-2-5` (out-of-scope) on issue #26 during decision D-PO-26-2-5. **Original scope note:** Flagged as out of scope in the approved PREQ. Known follow-up candidate if the same pattern is observed on those paths — a sibling issue keeps it visible. **Disposition rationale:** Issue creation, body edits, meta.json and seqfile updates still write directly to their final visible paths, so the crash-visibility class this feature closes for comments remains open there — lower blast radius (no cross-record identity collision), but the PREQ itself names it a known follow-up candidate. A sibling issue keeps it visible in the backlog instead of evaporating when #26 closes. This issue was deferred out of the parent feature's scope; it carries no PREQ yet. Run `/requirements --issue={new-number}` to flesh it out before planning.

jbr870 added the

labels

2026-08-13 08:18:01 +00:00

jbr870 referenced this issue

2026-08-13 08:18:10 +00:00

local-fs comment integrity — portable mtime pinning + atomic post_comment #26