Claude/coronation index audit ch97si - #84
Merged
Merged
Conversation
Adds docs/updates-page-design.md, a written design for a What Changed page covering the last 90 days. Key finding driving the design. Neither signal the portal holds today supports a truthful derived changelog. lastVerified is a verification date, not a change date, and clusters in bulk import batches. Git history is 44 days deep, so a 90-day window reads 2,124 of 2,125 content files as newly added. A derived feed would bury the two policy changes a reader needed this quarter under 750 rows of citation authoring. Proposal is a curated collection at content/updates/, authored as changes happen, with a four-kind by three-impact taxonomy, a /updates reference route, and reuse of the citation registry for authority chips. No new UI primitives. Includes a three-phase build plan, six real seed entries, and five open decisions. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SwhE46poJAGG8rArPXratZ
Builds the design in docs/updates-page-design.md with the five open decisions resolved. The page answers one question for a reader coming back after a few weeks. Did anything I rely on change, and do I need to act. Why curated rather than derived. lastVerified records a source check, not a change, and it clusters in bulk import batches, 153 pages share one date. Git history is 44 days deep, so a 90-day window reads 2,124 of 2,125 content files as new. Either signal would bury the two policy changes a Marine needed this quarter under 750 rows of citation authoring. New collection at content/updates/, validated by updateSchema. Four kinds crossed with three impact levels. Authority resolves through the citations registry by id, so every entry carries a working chip at no extra cost. An update record carries no lastVerified and no source object, it is an event rather than a page. Sync gains the cross-file checks zod has no reach for. Citation ids against the registry, affectedPages against the route shape, supersededBy against sibling slugs, plus a log line naming every entry aged out of the window. Decisions as built. Updates took the fifth mobile tab and recently-viewed moved to the topbar reference menu as History. Verification sweeps collapse under the timeline. The window is fixed at 90 days with no control and no archive, recorded in CLAUDE.md Section 4.6 as the standing authoring rule. Display title reads What Changed, Updated, or Added. Seeded with six real entries from the last three weeks. Six against 2,125 file changes in the same window is the argument for the design. Also swaps the home Latest Updated strip, which sorted role pages by lastVerified and presented import batches as news, and registers humanitarian-transfer in marines-categories so the page added on 2026-08-02 reaches the sidebar. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SwhE46poJAGG8rArPXratZ
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR successfully adds a curated changelog feature with an updates collection tracked under /updates. The implementation follows the established codebase patterns and includes comprehensive validation.
Key additions:
- Updates collection with 90-day trailing window
- Schema validation for update entries (kind, impact, roles, citations, affected pages)
- Build-time validation against citation registry and route shapes
- Server-side loader functions with proper filtering
The implementation is solid with no critical defects found. All validation logic is properly implemented and the code follows security best practices.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
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
2 participants
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
Type of change
Role scope
If this PR touches role-tagged content or routes, list affected roles:
Pre-flight checklist
npm run content:syncclean).lastVerifiedreflects a real source check (not a no-op refresh).Citationchips andReferencePill).globals.css, no hardcoded hex.npm run lintclean.npm run type-checkclean.npm run buildclean.Sources cited
Risk and rollback