admin/LithosAnanake
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Stage D batch 6: mama_forth_words.c group 4 -- identity/crypto words (FABRIC-3.md §XXXII.6)
Build / build-amd64-iso (push) Canceled after 0s
Details
Build / build-aarch64-iso (push) Canceled after 0s
Details
Build / build-riscv64-img (push) Canceled after 0s
Details

Browse Source 
MINT + mint_pop_string()/ZUSE-ELIGIBILITY-ADD/ZUSE-ELIGIBLE?/
ELEVATE-PUBKEY-UNPACK, 10 sites. mint_pop_string() gained a field_name
parameter so its diagnostics name which of MINT's four string
arguments failed (phone/email/username/full_name), rather than a
generic message that would leave the operator guessing. Diagnostic
placement matched each function's own sibling convention where one
exists (ZUSE-ELIGIBILITY-ADD), log_message() default otherwise.

Three-arch clean qemu acceptance passed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BWpNjdwPtFLuVLaAq44L9K
This commit is contained in:
Robert Allan James
2026-09-15 19:53:47 -04:00
co-authored by Claude Sonnet 5
parent 8b5300fc4f
commit 90c86c6006
10 changed files with 27201 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files
FABRIC-3.md
+15
View File
@@ -4654,3 +4654,18 @@ own WIREBIND attach (every boot) drives `HERA-BLK-ATTACH-REQ`'s `MSG-SEND`, whic
`SWITCH-MARK-WORK` -- so this fix's own most safety-critical path is exercised by the standard
acceptance boot itself, not just compiled.
**Batch 6 -- DONE, 2026-09-15: group 4, identity/crypto (`MINT` + `mint_pop_string()`,
`ZUSE-ELIGIBILITY-ADD`, `ZUSE-ELIGIBLE?`, `ELEVATE-PUBKEY-UNPACK`) -- 10 sites.**
`mint_pop_string()` gained a `field_name` parameter (`"phone"`/`"email"`/`"username"`/
`"full_name"`, one per call site) so its three now-diagnosed guards name which of `MINT`'s four
string arguments actually failed, via `console_println()` -- a generic message would have left
the operator guessing which one, defeating the point of fixing a silent-minting failure.
`MINT`'s own `restrict?`-flag guard matches the same convention. `ZUSE-ELIGIBILITY-ADD` matched
its own existing `console_println()` sibling ("FAILED -- fence write error"). `ZUSE-ELIGIBLE?`
and `ELEVATE-PUBKEY-UNPACK` have no sibling guard in their own function bodies -- kept
`log_message()`, the file's established default.
**Verified:** three-architecture `clean qemu` acceptance (amd64/aarch64/riscv64) passed, standard
regression unaffected -- including the `mint_pop_string()` signature change compiling cleanly
across all four call sites.