docs(ledger): back-fill refuel_log migrations + record FDQ-56 id=207 scrub - #26
Merged
Conversation
…scrub supabase/applied_migrations.md was missing the two grey_two.refuel_log migrations (applied Forces-lane during Phase F but never ledgered) and needed the FDQ-56 single-row security scrub recorded. Adds three entries: - 20260715120000_create_refuel_log (sha256 344c34fc…c1bed) — the audit table (15 cols, 3 indices); notes the append-only-omission caught by grant verify. - 20260716090000_refuel_log_append_only (sha256 1241bb7e…c9a21) — FDQ-52 corrective: REVOKE UPDATE/DELETE/TRUNCATE from grey_pipeline_rw. - id=207 error_detail scrub (FDQ-56) — owner-cred UPDATE redacting a keyed RPC URL persisted before the redactError() choke point; UPDATE 1 (1 of 208 rows), has_url_after=f, error_class retained, marker in place. Timestamps anchored to DB-derived bounds (first refuel_log row 2026-07-16 23:38:46Z; row 207 ticked_at 2026-07-17 20:47:13.756845+00). schema_migrations untouched throughout (psql apply, not CLI push). Docs-only; no code, no tag. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Back-fill refuel_log migrations + record the FDQ-56 id=207 scrub
supabase/applied_migrations.mdwas missing the twogrey_two.refuel_logmigrations (applied Forces-lane during Phase F but never ledgered), and the FDQ-56 single-row security scrub needed recording. Docs-only; no code, no tag. Independent of #25.Entries added
20260715120000_create_refuel_log344c34fc…c1bed20260716090000_refuel_log_append_only(FDQ-52)1241bb7e…c9a21error_detailscrub (FDQ-56)The scrub, for the record
Owner-cred
UPDATEredacting a keyed Alchemy RPC URL that row 207 persisted before the FDQ-56redactError()sink-layer choke point landed (#24,e6b3279):UPDATE 1— 1 of 208 rows;has_url_after = f;error_class = TransactionExecutionErrorretained; marker in place.grey_pipeline_rwis INSERT/SELECT-only (FDQ-52).grey_two.refuel_logonly; zero contact with any othergrey_twotable or anywpv_*. The 52 cosmetic public-URL rows (no key) left as-is per Forces ruling.supabase_migrations.schema_migrationsuntouched throughout (psql apply, not CLI push). Timestamps anchored to DB-derived bounds; exact apply times were not separately recorded.🤖 Generated with Claude Code