docs(llms): surface deploy-failure auto-debug path + CI discoverability guard#196
Merged
Merged
Conversation
…ty guard Closes the agent-discoverability half of the failure-diagnosis CI program: an agent that hits a failed deploy must be able to find, from llms.txt alone, that the classified cause is served back over HTTP — and that can't silently regress. - public/llms.txt: synced to content-repo HEAD (PR #27, a10699f) — adds the "Debugging a failed deploy (agent self-recovery)" section + the /docs/troubleshooting-deploys.md reference (the /events autopsy loop: reason + last_lines + hint → fix → redeploy → re-poll). - src/lib/llmsContract.test.ts: new CONTRACT_MARKERS row asserting llms.txt contains BOTH the 'troubleshooting-deploys' reference AND the '/api/v1/deployments/:id/events' debug surface — so a content sync or docs edit that drops the debug path reds CI (verified: removing the events marker fails the test by name). - scripts/fetch-content.mjs: adds the same two markers to the llms.txt requireMarkers lock-step guard — a future upstream sync missing them PRESERVES the committed copy instead of reverting the documentation (rule 22). Pairs with the FUNCTIONAL live proof in e2e/live-ui-failure-diag.spec.ts (#195): discoverable AND demonstrably working. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
mastermanas805
enabled auto-merge (squash)
June 6, 2026 05:45
size-limit report 📦
|
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.
What
Closes the agent-discoverability half of the failure-diagnosis CI program: an agent that hits a failed deploy must be able to find, from
llms.txtalone, that the classified cause is served back over HTTP — and that can't silently regress.Source:
docs/ci/02-FAILURE-DIAGNOSIS-AND-AUTODEBUG.md; pairs with the functional live proof ine2e/live-ui-failure-diag.spec.ts(#195).Changes
public/llms.txt— synced to content-repo HEAD (PR perf: lazy-load secondary marketing pages to shrink main bundle #27,a10699f): adds the "Debugging a failed deploy (agent self-recovery)" section + the/docs/troubleshooting-deploys.mdreference (the/eventsautopsy loop:reason+last_lines+hint→ fix → redeploy → re-poll).src/lib/llmsContract.test.ts— newCONTRACT_MARKERSrow assertingllms.txtcontains BOTH thetroubleshooting-deploysreference AND the/api/v1/deployments/:id/eventsdebug surface. A content sync or docs edit that drops the debug path now reds CI (verified: removing the events marker fails the test by name).scripts/fetch-content.mjs— adds the same two markers to thellms.txtrequireMarkerslock-step guard, so a future upstream sync missing them PRESERVES the committed copy instead of reverting the documentation (rule 22).Verification
npm run gategreen (tsc + build + prerender + 1130 vitest, +1 = the new contract row)./api/v1/deployments/:id/eventsfrompublic/llms.txt→ the new row failed by name (expected the deploy-failure auto-debug path … to include the substring "/api/v1/deployments/:id/events"), then restored.requireMarkersguard is a no-op today (the sync applies cleanly).🤖 Generated with Claude Code