fix(catalog): generate search index, footer version, and standards grid from source#81
Merged
Merged
Conversation
…id from source [skip version] Three hand-maintained regions of docs/index.html had silently drifted and were not covered by sync-check: - The inline search-index block was frozen at 9 of 14 tools, so the five newest tools (developer-tools-mcp, cfx-mcp, blender, local-ai, screencast) were unsearchable on the live site (D1). - The footer version was hardcoded v1.9.5 against a real latest tag of v1.17.0 (D2). - The standards grid was missing born-green-contract and its count read 18 for 19 standards (F2). - docs/search-index.json was generated by aggregate_search.py but never fetched by the page; the page read only the inline block (F3). sync_from_registry.py now owns all four: it reconciles docs/search-index.json from the registry (preserving the scanned skill/rule/MCP-tool name arrays), mirrors it into the inline fallback block, sets the footer from VERSION, and generates the standards grid and count from the standards/*.md listing. Each new region is best-effort so a minimal catalog without a VERSION file or standards directory is left untouched. All four are covered by --check. setupSearch now fetches search-index.json at runtime with the inline block as the offline/file:// fallback, so the file and the embedded copy agree (P1n). aggregate_search.py merges with the existing index so refreshing without a full fleet checkout no longer discards previously scanned names. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: TMHSDigital <TMHospitalityStrategies@gmail.com>
github-actions
Bot
added
the
documentation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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
Fixes the four catalog data-integrity findings from the presentation audit (
site-audit.md): D1, D2, F2, F3, P1n. No VERSION bump (site/data change,[skip version]).Three hand-maintained regions of
docs/index.htmlhad drifted and were not covered bysync-check.sync_from_registry.pynow owns them so they cannot drift again.Findings addressed
search-indexwas frozen at 9 of 14 tools; the 5 newest (developer-tools-mcp, cfx-mcp, blender, local-ai, screencast) were unsearchable on the live site.v1.9.5vs real latest tagv1.17.0; now sourced fromVERSION.born-green-contract; count read 18 for 19 standards. Grid + count now generated from thestandards/*.mdlisting.docs/search-index.jsonwas generated but never fetched.setupSearchnow fetches it at runtime with the inline block as the offline/file://fallback.aggregate_search.pymerges with the existing index so a partial-checkout refresh no longer discards scanned names.Verification
python scripts/sync_from_registry.py --checkpasses.🤖 Generated with Claude Code