feat(supabase): R5.5 upload-sheet-assets in Rust, R5.4 caps and FLOOR clarification

Core rules curation::upload (manifest, local destination, bytes through the SVG reader,
plan from observed state); binary upload-sheet-assets over ureq (handshake, no overwrite,
confirm after verify, bounded retries, key never printed); pnpm assets:upload repointed,
e2e:sheet-assets for the local stack. 4 MiB cap on changes.json and references.json.
FLOOR clarification for audit prose with its negative proof.
This commit is contained in:
bchanot committed 2026-10-23 21:15:22 +02:00
1 parent 637ea6334c
commit 2c445063a4
20 files changed
+1595 -21

No files matched your search

@@ -58,3 +58,13 @@ switch, no release, no deploy.
freezes what Prettier does to authored Markdown, from which the port's `UnsupportedMarkdown` guard is derived (C2 read as
"byte for byte with the TypeScript, or a loud refusal declared in RUST.md §11.14"). It is added, never a frozen file
changed; C7 excepts it with `review-synthetic.json`.
- 2026-10-23 (owner « Validation R5.4 et autorisation conditionnelle R5.5 » §2, FLOOR): the `floor-guard.sh` hits on a
Markdown line under `.claude/audits/**` that only quote one of the guard's suppression keywords in prose (the audits
state that none was added) are requalified as descriptive mentions.
The clarification does not reach executable code, active contracts, production scripts, generated artefacts or a real
removal: those findings keep failing. Past audit reports are not edited. Proof: `scripts/floor-clarification-check.sh`
(requalifies by path and kind, then runs a throwaway repo where a real keyword in `src/*.ts`, `src/*.rs` and in an
active contract is still reported). Result on this branch vs develop: 20 findings, 19 requalified (audit prose), 1 kept:
a STUB marker in `.claude/memory/evals.md:205` (a quoted stub-marker phrase in a heading, append-only registry), outside the
owner's clarification, reported to the owner and not requalified.