issues: #46 provenance thread appended (deferred)
Message
issues: #46 provenance thread appended (deferred)
Diff
.forge/issues/df02571d-47b7-4dab-9077-73ecb58da12e/issue.md+23 −0
--- a/.forge/issues/df02571d-47b7-4dab-9077-73ecb58da12e/issue.md+++ b/.forge/issues/df02571d-47b7-4dab-9077-73ecb58da12e/issue.md@@ -7,6 +7,16 @@ labels:77 assignees: []88 milestone: null99 created: 2026-09-08T10:21:54.787248721Z10+updated: 2026-09-08T21:49:03.109262846Z11+---12+id: df02571d-47b7-4dab-9077-73ecb58da12e13+title: 'f0rge repo list: discover f0rge repos on the box (DEFERRED — owner deciding scan vs remember)'14+state: open15+labels:16+- deferred17+assignees: []18+milestone: null19+created: 2026-09-08T10:21:54.787248721Z1020 updated: 2026-09-08T21:45:18.210985138Z1121 ---1222 STATUS: DEFERRED by owner 2026-09-08 — do NOT work until the owner@@ -65,3 +75,16 @@ same class as #37 parse hints).6575 STILL DEFERRED. Owner deciding: scan vs remember; how --repo6676 validates target state (uncommitted .forge? concurrent agents? —6777 likely just document + refuse on dirty .forge).78+79+PROVENANCE THREAD (owner Q 2026-09-08, appended): can f0rge tell80+local vs -R external filing? Only at create-time — the resulting81+file is identical either way; a "via -R" marker is a STAMP, not a82+distinction. Judgement: dont stamp the entity (derived state; gh83+doesnt; and provenance must never become policy/trust tiers).84+Two clean audit homes: (a) commit-level — external filing commits85+a distinct message ("issue from <repo>: #N") so provenance is a86+git-log query, zero schema; (b) optional author field (spec87+already has Optional author on comments; gh shows issue author)88+auto-stamped from git config or the -R remote — the upgrade path89+if visible provenance is ever wanted. Lean (a); never policy on90+provenance.