Repository navigation
feat(crosscheck): add the Spec Kit studies and a landing page with a study index - #147
Merged
Merged
Conversation
…study index The root becomes a landing page that lists the studies. The EVerest study moves to /studies/everest-ocpp/, and /everest.html, /glossary.html and old root fragment links forward to it. /studies/spec-kit/ presents the 28 defects reported against GitHub's Spec Kit (#5071 to #5098): what each contradicts in Spec Kit's own documentation and its upstream state on 2026-11-10. 19 have a merged fix, 8 have a fix open and 1 has neither. /studies/spec-kit-expressions/ looks at the three workflow-expression reports. Both pages render from spec-kit-study.json. check-site fails if a count the prose repeats drifts from that record. The reproductions were not rerun for this change, and the pages say so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NFQZoTNGDVvV9v3Ycp6Ruc
The method now comes from the transcript of the 2026-10-22 session. CGV ran first, and an agent triaged its 39 errors as holding no real bug. Eight /reason subagents then searched one slice each, and a finding counted only when a reproduction showed it. 31 findings became the 28 reports. The six findings left unfiled because an open issue or pull request covered them are now listed. The pages now attribute the human re-run to the reports, because the transcript does not show it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NFQZoTNGDVvV9v3Ycp6Ruc
Harry confirmed re-running every reproduction before filing, so the Spec Kit pages now state it, not attribute it to the reports. The count now reads 38 reproduced findings: 31 in the 28 reports, 6 already covered upstream, and 1 emailed to GitHub's security team with no reply. Nothing about that report's subject is published. check-site fails if those parts stop adding up to 38. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NFQZoTNGDVvV9v3Ycp6Ruc
The Spec Kit page, intent and journal no longer mention whether GitHub's security team replied. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NFQZoTNGDVvV9v3Ycp6Ruc
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.
Tier: 2
Intent: intent/2026-11-10-spec-kit-studies.md
Spec: intent/2026-11-10-spec-kit-studies.md
Why
On 2026-10-23 Harry filed 28 defect reports against GitHub's Spec Kit (github/spec-kit #5071 to #5098), found with CGV and Crosscheck. The site held one study at its root, so a second study had nowhere to go.
What changed
/. A study index, three paragraphs on the tool, and the install commands./studies/everest-ocpp/, with its glossary and record./everest.html,/glossary.htmland old fragment links on the root (/#witness,/#q-proof&s=tested) forward there, fragment included. The study page carried its head metadata twice; the second copy is removed./studies/spec-kit/lists the 28 reports by area. For each it gives what goes wrong, which line of Spec Kit's own documentation, docstring, test or code it contradicts, and its upstream state on 2026-11-10: 19 with a merged fix, 8 with a fix open, 1 with neither. It uses the EVerest page's questions, strengths and entries./reasonsubagents each searched one slice of the source. A finding counted only when a reproduction showed it./studies/spec-kit-expressions/looks at #5071, #5072 and #5073 on the workflow expression evaluator: the recorded outputs, what Jinja2 gives, and what changed upstream. An agent's reading of main's source is marked Not yet reached.site/studies/spec-kit/spec-kit-study.jsonfeeds both pages throughscripts/site-spec-kit.mjs.check-site.mjsfails if a count the prose repeats drifts from it.render-site-images.mjsgains--cards-onlyand aPLAYWRIGHT=1path, because Chrome's command-line screenshot did not finish in a container. The two EVerest cards are unchanged.Scope
site/LAUNCH.md, updated for the new paths.Blast radius
Only the static site under
site/, its Node build, check and image scripts and their tests,PRODUCT.md, the site journal and the new intent. No plugin, MCP server or CGV code is touched, and no protected surface.Verification
node scripts/build-site.mjs --check,node scripts/check-site.mjsandnode --test scripts/*.test.mjspass (146 tests). Five new site tests cover the Spec Kit record checks, the hand-written counts, rebuild freshness, old-link forwarding and links inside study directories.node scripts/check-public-site.mjs http://127.0.0.1:8765/passes against a local server.Generated by Claude Code