chore(registry): refresh gmail-* + yep-memory rendered cards#56
Closed
drknowhow wants to merge 1 commit into
Closed
chore(registry): refresh gmail-* + yep-memory rendered cards#56drknowhow wants to merge 1 commit into
drknowhow wants to merge 1 commit into
Conversation
Follow-up to two upstream fixes that landed earlier today: - drknowhow/install-manifest-spec#33 — gmail-*.json: drop dead links to private drknowhow/Yep, repoint at spec-repo URLs - drknowhow/yepgent-site#107 — yep-memory.v0.4.json: drop the same dead links, repoint at yepgent.com + toolspace registry surface This PR re-syncs the gmail-* example files into this repo via sync_from_spec.py (they're CI-gated for byte-identity with the spec) and rebuilds the rendered registry pages so the live cards reflect the new homepage / docs / issues URLs. Companion to vi-federation self-link fix (#53). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Owner
Author
|
Closing as superseded — the dead-link fixes this PR set out to make already landed via #54 (repoint drknowhow/Yep links + re-sync Gmail examples), #55 (vi-federation timestamp), and upstream install-manifest-spec#33. Verified on current main: committed examples/*.json are byte-identical to the spec (LF-normalized), and build_registry_pages --check + build_changelog_page --check both pass clean. This branch was built from a stale local install-manifest-spec clone (pre-#33), so its commit would actually re-introduce the dead drknowhow/Yep links rather than remove them. The only fresh-rebuild delta vs main is wall-clock timestamp churn, which the CI --check gate pins. Nothing on main is broken; no replacement PR needed. |
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
Follow-up to two upstream link-fixes that landed earlier today:
This PR re-syncs the gmail-* example files (CI-gated for byte-identity against the spec) via `scripts/sync_from_spec.py` and rebuilds the rendered cards via `scripts/build_registry_pages.py` so the live registry reflects the fresh URLs. Companion to #53 (vi-federation self-link).
Audit context
2026-06-19 registry audit found
drknowhow/Yepis private → public visitors hit 404s on every link to it across the 3 gmail-* example cards and the yep-memory card. The upstream manifest sources were fixed first; this PR is the catch-up so the rendered HTML actually shows the new URLs.Test plan
python scripts/sync_from_spec.py --checkpasses locallypython scripts/build_registry_pages.py --checkpasses locally🤖 Generated with Claude Code