docs: the public-scan surface, and seven more lessons for the log - #71
Merged
Conversation
The README shows the feature the way it lands hardest: the deployed instance
scanning its own repository — seven workflows, four clean, three findings, each
one a registered, test-enforced exception. The screenshot is captured from the
live deployment, and the demo guide gains the step that uses it: scan a
repository the audience picks.
Engineering log grows from 18 entries to 25, in the established shape — what
was wrong, how it was found, why nothing caught it, what changed, what prevents
recurrence:
19. A rule demanded a setting GitHub rejects (golden corpus, first run)
20. Deploy was dead for a week and reported nothing (Actions allowlist vs bot)
21. The deploy gate measured the wrong instance, twice (liveness, then the
outgoing process answering ready)
22. A stale response wiped newer results (effect cancellation)
23. Endpoint options no test host could influence (pre-Build snapshot vs DI)
24. The strongest claim ran only in production (the transport seam)
25. A fix that traded one silence for another (no empty catch blocks — house
rule, CodeQL-enforced)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Documentation catch-up for everything that shipped today.
README
The public-scan feature is now shown the way it lands hardest: the deployed instance scanning its own repository — 7 workflows, 4 clean, 3 findings, each a registered, test-enforced exception. New screenshot (
04-public-repo-self-scan.png) captured from the live deployment via Playwright; no OpenAI credit spent, unlike the full capture script, because the public tab needs none.Demo guide
New step between the scenario walkthrough and exports: scan a repository the audience picks. If they hesitate, scan this repository itself — three documented findings close harder than a clean report.
Engineering log: 18 → 25 entries
Each in the established shape (what was wrong / how found / why nothing caught it / what changed / what prevents recurrence):
startup_failurehas no logsBuild()config snapshot vs DIDocs and one PNG only; no code changes.