Repository navigation
docs: sync test count and Supabase migration status in README and docs - #70
Merged
Merged
Conversation
#69) - README: badge/copy 9 -> 15 tests; list all suites under Tests section - TECHNICAL_DEBT: close TD-02, metadata lives in Supabase; residual risk is deploy-time env vars - DOCUMENTACION_TECNICA / TECHNICAL_DOCUMENTATION: date -> August 2026 and align asset metadata with Supabase-backed assetMetadata.ts
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Summary
Syncs README and docs/ with the current state of the repo — test count, documentation dates, and TD-02 status — after #66 landed and Supabase env vars got configured in Vercel.
Changes
describeblocks) with the 6 previously undocumented cases (technician re-registration, unregistered technician, mismatched technician signer, decommission with active escrow, decommission with drained vault,complete_maintenancereplay).docs/DOCUMENTACION_TECNICA.md/docs/TECHNICAL_DOCUMENTATION.md: "última actualización" / "last updated" synced to August 2026 in both.docs/TECHNICAL_DEBT.md: TD-02 markedCerrado (#69)with its own section — metadata lives in Supabase'sassetstable viautils/assetMetadata.ts; residual risk reclassified as deploy-time env var configuration, not code, with mitigation referenced indocs/DEPLOYMENT.md.docs/ARCHITECTURE.md: spot-checked against the program's actual current milestone — no changes needed, table already accurate.TECHNICAL_DOCUMENTATION.mdcaught up to its ES counterpart on 4 stale localStorage/assetNames.tsreferences and missingevidence.ts/supabase.tsutility entries.Deliberately unchanged
ISSUES_PROPUESTOS.md,TESTING.md,RUNBOOK.md— out of scope, planning/historical docs not covered by this issue.Testing
anchor testoutput (15 passing, confirmed via WSL run) — not just a staticit(count.Flagged for a future issue (out of scope here)
ARCHITECTURE.md,DOCUMENTACION_TECNICA.md, andTECHNICAL_DOCUMENTATION.mdcover overlapping ground (PDAs, instructions, architecture layers) — candidate for consolidation.TECHNICAL_DOCUMENTATION.md(EN) still doesn't document the evidence flow that its ES counterpart covers (sections 4/6b), and its folder structure still references a nonexistentclient/directory.Closes #69