Repository navigation
Improve portfolio accessibility, blog discovery, release reliability and admin recovery - #23
Merged
Merged
Conversation
…t recovery backlog
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
13 tasks
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
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.
Implements issue #20 items 1, 2, 4, 5, 6, 7, 8, 9 and 10 while retaining the Naruto/cyber design.
Validation: 37 Jest suites / 372 tests, TypeScript, targeted ESLint and production build pass. Disposable MongoDB tests pass for archive preservation, all 11 content collections, atomic audit failure rollback, soft deletion, stale restore rejection, backup round trips, import ledger and unique-conflict rollback. All 12 desktop/mobile browser scenarios passed, including real API/database publishing, contact persistence, Trash/restoration, backup download/upload and revoked sessions; the mobile admin scenario was rerun after adding a hydration readiness assertion. CI now runs these integrations and browser scenarios.
Operational details: optional deletedAt fields and a ContentRevision collection/indexes; use the normal prisma db push setup for indexes. Builds require a reachable populated DATABASE_URL. Backups are content-only, limited to 3 MB / 1,000 records; they include private bounty details and exclude credentials, sessions, inbox/client requests, old revision history and media binaries. Tests use synthetic localhost databases and do not write production content. See docs/portfolio-improvements.md.
Authentication upgrades and portfolio case-study content from #20 remain separate.
Additional validation: the existing concurrent throttle/import suite also passes after ensuring nested interactive callers share one content/history transaction; a regression test checks rollback of both. Mobile laboratory observation: LCP 888 ms, CLS 0.0167, five font requests / 131,626 bytes, no page errors or horizontal overflow; observed long-task blocking remains 2,268 ms under 4× CPU throttling with synthetic local data. These are not production field metrics. The diagnostic captures only the viewport to avoid oversized full-page GPU allocations.
Final verification for 0e45f64: GitHub Checks run #32 passed, including all 12 browser scenarios in one run (35.8 seconds), all database integrations, TypeScript, lint, unit tests and production build. Vercel preview READY: https://bikram-6mw6gq2pq-modhack2003s-projects.vercel.app . PR is open and mergeable; production has not been promoted.