Artifact 5b93933a94ff98ce0607e4a7929b13c59a96459d0b3a46a7babaa25b6a8e4cd4:
- File
internal/harness/protect_test.go
-
2026-08-26 23:24:05
— part of check-in
[2a68c15ebf]
on branch protect-5
— RFC 0007 phase 5: the matrix, driven through the forge
Every row of the RFC's table, the way a person or a client would do it: the forge's accept through the API as owner and non-owner; a clone's accept pushed through the sync gate, refused whole with the branch named, then admitted for the owner with no reply posted; a stock fossil client's merge refused; branching off trunk and pushing to an unprotected branch admitted; a forged accepted reply recorded as a claim. A branch continued past its merge stays accepted.
Compatibility and disposability as the RFC states them: a clone's artifacts are identical with the row present or absent, and the record renders identically before and after the row, and across the section-11 wipe.
The disabled control with its reason is proved in the web package, where a viewer has an identity — and proving it found the landing page asking MayLand about nobody: the viewer now travels with the read. Three rows are proved elsewhere and named in the file so the matrix reads complete. (user: dmestas, size: 16956) [annotate] [blame] [check-ins using]
- 2026-08-26 23:51:55 — part of check-in [763b776f6f] on branch trunk — Landed phase 5: every row of the RFC's table, proved the way a person would do it. (user: ai-local, size: 16956) [annotate] [blame] [check-ins using]
-
2026-08-26 23:24:05
— part of check-in
[2a68c15ebf]
on branch protect-5
— RFC 0007 phase 5: the matrix, driven through the forge