···3838- `com.atproto.sync.requestCrawl`
3939 The reference runtime still drives crawler notices internally, but the current official build does not expose the endpoint directly as a comparable external surface.
4040- `com.atproto.sync.notifyOfUpdate`
4141- Locally covered in `t/uncovered-endpoints.t`; not wired as a comparable public surface in the current official runtime.
4141+ Locally covered in `t/crawler-status-surfaces.t`; not wired as a comparable public surface in the current official runtime.
4242- `com.atproto.admin.updateAccountSigningKey`
4343 Locally covered in `t/admin-account-surfaces.t` and aligned to lexicon-void response semantics; no matching official external endpoint wiring was found in the current reference build.
4444- `com.atproto.admin.searchAccounts`
+6-8
docs/TEST_AUDIT.md
···1313The current baseline for saying "the audited suite is green" is:
14141515- `prove -lr t`
1616- - latest full green result in the realigned Meridian worktree: `Files=59, Tests=3057`
1616+ - latest full green result in the realigned Meridian worktree: `Files=60, Tests=3061`
1717- `prove -lv t/server-auth.t`
1818- `perl -c script/differential-validate`
1919- `PERLSKY_RUN_REFERENCE_DIFF=1 prove -lv t/reference-differential.t`
···116116Current suite counts by bucket:
117117118118- `direct reference differential`: `5`
119119-- `audited local regression`: `41`
119119+- `audited local regression`: `42`
120120- `local correctness/infrastructure`: `13`
121121122122| Test file | Bucket | Current note |
···135135| `t/catalog.t` | local correctness/infrastructure | lexicon/catalog exposure smoke |
136136| `t/cors.t` | local correctness/infrastructure | CORS and preflight behavior |
137137| `t/crawlers.t` | audited local regression | outbound crawl notification semantics |
138138+| `t/crawler-status-surfaces.t` | audited local regression | isolated local crawler host notification/status endpoint coverage for `notifyOfUpdate` and `getHostStatus` |
138139| `t/crypto-interop.t` | direct reference differential | pinned upstream crypto fixture coverage |
139140| `t/delete-account.t` | audited local regression | reference-style account deletion flow using DID, password, and action token without a live bearer session |
140141| `t/discovery-surfaces.t` | audited local regression | isolated local discovery-surface coverage for endpoint catalog wiring, lexicon lookup, handle availability, and `listReposByCollection` |
142142+| `t/describe-repo-surfaces.t` | audited local regression | isolated `describeRepo` correctness coverage for collection listing and DID-doc-derived `handleIsCorrect` semantics |
141143| `t/email-confirmation.t` | audited local regression | intentionally testing-friendly email flow plus strict missing-email and invalid-email validation semantics |
142144| `t/email-update-helper.t` | audited local regression | shared email-update helper normalization, token revocation, and duplicate-email error semantics |
143145| `t/event-stream.t` | audited local regression | wire-format, malformed frame, and event decoding coverage |
···179181| `t/store-sqlite.t` | audited local regression | store-level session, invite, label, and repo persistence behavior |
180182| `t/temp-endpoints.t` | audited local regression | isolated local coverage for `com.atproto.temp.*` semantics and admin credential revocation behavior |
181183| `t/tid-repair.t` | local correctness/infrastructure | TID repair and recovery helpers |
182182-| `t/uncovered-endpoints.t` | audited local regression | now a very small pragmatic safety-net for `describeRepo` correctness and crawler host notification/status edges that still do not have a better thematic home |
183183-184184### Broad Mixed Suites
185185186186-The broadest suites are green and audited, but they still mix several categories of behavior inside the same file:
186186+The broadest suites are green and audited, but a small number still mix several categories of behavior inside the same file:
187187188188- `t/extended-api.t`
189189 Carries real conformance value for `applyWrites`, but it is now much narrower and mostly acts as a focused repo-write regression suite.
190190- `t/external-surface.t`
191191 Carries strong external-surface coverage for repo/blob export and missing-blob listing. It is cleaner after moving discovery, label-RPC, and account-status checks into dedicated suites, but still remains broader than a single-endpoint conformance file.
192192-- `t/uncovered-endpoints.t`
193193- Exists specifically to stop a few lesser-used local endpoints from falling out of coverage; it is much narrower now that the temp, invite, and admin-account blocks have moved into dedicated suites, but it should still be read as a pragmatic safety net, not as a pure reference-alignment suite.
194192195193## What This Audit Does Not Yet Claim
196194···2132114. decide whether to tighten admin auth to reference semantics or document the bearer shortcut as a permanent extension
2142125. keep local testing-only toggles, like the email-confirmation bypass, pinned in focused suites instead of letting broad mixed suites depend on them implicitly
2152136. keep narrowing the local `ServiceProxy` surface until every locally answered `app.bsky.*` field is either authoritative or explicitly documented as a local-only extension
216216-7. keep documenting broad suites like `t/extended-api.t`, `t/external-surface.t`, and `t/uncovered-endpoints.t` as mixed conformance-plus-product coverage rather than over-claiming that every assertion is a pure reference check
214214+7. keep documenting broad suites like `t/extended-api.t` and `t/external-surface.t` as mixed conformance-plus-product coverage rather than over-claiming that every assertion is a pure reference check
217215218216## Practical Reading Of The Current Status
219217