Add source-linked inspiration ledger - #339
Merged
Merged
Conversation
6 tasks
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.
Purpose
Give visible, specific credit to the tools and ideas that shaped CodeVetter. The owner selected the Reference Ledger design and asked for an exhaustive, detailed series derived from project discussions.
What changed
/inspirationwith search and area filters, plus 38 static notes at/inspiration/<slug>./api/ai, and agent indexes. No production dependency or server endpoint was added.Verification
pnpm build:landing: passed, including docs merge and internal-link validation.node apps/landing-page-astro/scripts/verify-agent-surfaces.mjs: 871/871 sitemap routes have Markdown and API catalog entries; privacy parity passed.pnpm lint,pnpm knip:strict,pnpm quality:cycles,pnpm quality:change-size, andnode scripts/check-docs.mjs: passed.Tracks #337. Close the issue after deployment and live smoke.