| Comment: | Create new branch named "slice-serve-coverage" |
|---|---|
| Timelines: | family | ancestors | slice-serve-coverage |
| Files: | files | file ages | folders |
| SHA3-256: |
12dd6240d75f21ad4d78b208fefbeb3e |
| User & Date: | dmestas on 2026-07-24 14:42:39.848 |
| Other Links: | branch diff | manifest | tags |
|
2026-07-24
| ||
| 14:42 | Create new branch named "slice-serve-coverage" closed check-in: 12dd6240d7 user: dmestas tags: slice-serve-coverage | |
|
2026-07-23
| ||
| 17:02 |
Repository State draft: carry the unclassifiable-artifact clarification
Regenerated from the RFC suite after the erratum repo-state-00-s4-unclassifiable-artifact was applied. New §4.4 states what assembly does with a stored artifact classification rejects: an artifact whose octets hash to the name it is stored under is opaque to repository state and MUST NOT fail the assembly, while one whose octets do not hash to its name is a distinct integrity failure and MUST be rejected. The remaining §4 subsections renumber behind it. The draft was previously silent on this, and that silence was the trap: an implementation conforming to both drafts could reject an artifact per the required-card rule and then treat that rejection as fatal, which made the canonical fossil repository unassemblable. src/update.zig implements the rule this text now carries. check-in: 42e1faa9fc user: dmestas tags: trunk, version-0.1.2 | |