Add an inspiration article series for tools that shaped CodeVetter

[sarthakagrawal927]

Why

The owner wants CodeVetter to give thoughtful credit to tools that influenced the product. Current site content compares some products as competitors, but it has no dedicated place to explain what we genuinely learned from them. The series should be appreciative, specific, and technically honest.

What

Add a static /inspiration index and one editorial article per tool with a concrete lesson in the project record at /inspiration/<product-slug>. The owner requested an exhaustive, detailed series derived from tools discussed while building CodeVetter. Each article names a concrete idea we learned, links to the tool's primary source and the relevant CodeVetter research, explains our own implementation boundary, and avoids implying affiliation or copying another product's identity. Keep the site lean: reuse Astro and current infrastructure; add no runtime dependency or server feature.

Out of scope: competitor rankings, live pricing tables, generated bulk pages, new app features, or claims that CodeVetter implements an admired feature without evidence.

Design

Use a typed content registry for the source-linked notes, static Astro routes, and one index. The owner selected direction C, Reference Ledger, from three visual previews. Reuse the existing navigation/footer and build-time agent-readable surfaces. Build-time validation should catch duplicate slugs and missing primary links. The new pages deploy with the existing manual landing workflow; keep public release and download claims tied to the actually published build.

Specs

Requirement: Attributable inspiration

Each page SHALL identify the tool, the specific idea it influenced, and at least one direct primary source. It SHALL distinguish CodeVetter's implemented behavior from an aspiration or research idea. It SHALL not imply endorsement or affiliation.

Scenario: Reader opens an inspiration article

• WHEN a reader opens /inspiration/<product-slug>
• THEN they see the named tool, an appreciation grounded in a concrete design or engineering principle, a source link, and a clear account of what CodeVetter adopted or deliberately left different.

Requirement: Discoverable static series

The index SHALL link every approved article, and the articles SHALL be included in the static sitemap and agent-readable export. Unknown slugs SHALL not silently become generic content.

Scenario: Site build

• WHEN the landing site builds
• THEN each approved route exists and the site verification checks pass without a new runtime dependency.

Requirement: Visual and release consistency

The series SHALL use the selected CodeVetter visual direction, work at 390, 768, and 1440 px, remain keyboard-readable, and match the published product state at deployment time.

Scenario: Public share

• WHEN the owner shares the website
• THEN /inspiration and each article load publicly, source links resolve, and the download page points to the intended published release.

Tasks

• Derive the tool list from the project log, research survey, competitive landscape, and integration decisions; distinguish design references from tools only surveyed.
• Present three visual systems with representative previews and record the owner's selection: C, Reference Ledger.
• Research each approved tool from primary sources and draft bounded, attributable copy.
• Implement the static index and article routes with existing site infrastructure.
• Validate content, accessibility, responsive output, sitemap/agent surfaces, and production build.
• Coordinate deployment with the CodeVetter release, then smoke the live pages and close this issue.

[sarthakagrawal927]

The owner selected Reference Ledger (direction C). PR #339 contains 38 source-linked static notes derived from the project log, competitive research, context-tool survey, OSS integration decision, and explicit Finder/DeepWork references. Local landing build, 871/871 sitemap/Markdown/API catalog parity, lint, Knip, cycles, docs, and change-size checks passed. Exact-head CI and live deployment smoke remain before closing this issue.