Skip to content

docs: the public-scan surface, and seven more lessons for the log - #71

Merged
bgard68 merged 1 commit into
mainfrom
docs/lessons-and-public-scan
Aug 24, 2026
Merged

docs: the public-scan surface, and seven more lessons for the log#71
bgard68 merged 1 commit into
mainfrom
docs/lessons-and-public-scan

Conversation

@bgard68

@bgard68 bgard68 commented Aug 24, 2026

Copy link
Copy Markdown
Owner

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):

# Lesson
19 A rule demanded a setting GitHub rejects — the golden corpus caught a false positive on its first run
20 Deploy was dead for a week and reported nothing — Actions allowlist vs Dependabot, startup_failure has no logs
21 The deploy gate measured the wrong instance, twice — liveness vs readiness, then the outgoing process answering ready
22 A stale response wiped newer results — effect guard runs at start time, promise resolves later
23 Endpoint options no test host could influence — pre-Build() config snapshot vs DI
24 The strongest claim ran only in production — the OpenAI transport seam
25 A fix that traded one silence for another — no empty catch blocks, house rule, CodeQL-enforced

Docs and one PNG only; no code changes.

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>
@bgard68
bgard68 merged commit 6ad7c51 into main Aug 24, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant