feat: record the pin a prose reread confirmed

A prose citation whose text lived under several pins stayed in
read again until the text changed, so fixnes, zesarux and emucorex,
exact at their pins, would have refused every later bump.
prose_written_at names the pin a reader confirmed; it settles the
readings and never overrides a history with one candidate.
This commit is contained in:
Abdessamad Derraz committed 2026-10-18 02:49:24 +02:00
1 parent a5f41511cc
commit 8a9d6919d9
7 files changed
+52 -1

No files matched your search

+5
View File
@@ -800,6 +800,11 @@
"type": "string",
"description": "Branch the port was read from, when it is not the default one."
},
"prose_written_at": {
"type": "string",
"pattern": "^[0-9a-f]{40}$",
"description": "The pin a reader confirmed every prose citation against. When the profile's history shows several pins under one text, profile_sync takes this one as the revision the text describes; it never overrides a single candidate."
},
"pin_frozen": {
"type": "string",
"description": "Why source_commit is held on purpose rather than followed. The profile is then judged against its own revision, like one pinned to a superseded tag: comparing it to HEAD says nothing and recaling would repoint its refs at code the build it documents never had."