Skip to content

Commit 11d8421

Browse files
committed
test(dogfood): the census re-anchors rest-server.ts's enforceAuth control 61 -> 64 for three comment-only mentions
Commit 1d79556 (the API-key lifecycle) added three prose mentions of `enforceAuth` to packages/rest/src/rest-server.ts: two in the docblock on `apiKeyLifecycleRefusals` and one in `computeExecCtx`'s outer catch. It added and removed no call site. The census counts the bare term, comments included, so the control moved 61 -> 64 while population, reach, blind spot and every other control on the row stayed as pinned. Re-anchored with a provenance note, as the row's earlier moves were; the control stays an exact count. Claude-Session: https://claude.ai/code/session_01YRp5z4kK6vgYkrdH97ztsy Co-authored-by: Claude <noreply@anthropic.com>
1 parent fa6a608 commit 11d8421

1 file changed

Lines changed: 15 additions & 1 deletion

File tree

‎packages/qa/dogfood/test/authz-probe-blind-spot.census.ts‎

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -631,6 +631,20 @@ export const PROBE_FILE_CENSUS: readonly ProbeFileReading[] = [
631631
// carries the move — the host literal's forwarder (`enforceAuth: (...a) =>
632632
// this.enforceAuth(...a)`, two) and the host interface's member
633633
// (`enforceAuth: RestServer['enforceAuth']`, two). No call site was added.
634+
// [commit 1d79556766] `enforceAuth` 61 -> 64, and nothing else on this row
635+
// moved: 70 / 19 / 51 and every other control re-derived unchanged.
636+
// ⛔ RE-ANCHORED, not relaxed: PR #23541 (#23367, the API-key lifecycle)
637+
// added three PROSE mentions and no call site, and `occurrences` counts the
638+
// bare term, comments included. At `fa6a6085c` they are
639+
// `rest-server.ts:2395` and `:2397`, the docblock on
640+
// `apiKeyLifecycleRefusals` ("so {@link enforceAuth} can answer it",
641+
// "every door that never reaches `enforceAuth`"), and `:3471`, the inline
642+
// comment in `computeExecCtx`'s outer `catch` ("for `enforceAuth`, which
643+
// answers its `403` and code"). The same commit edited `enforceAuth`'s own
644+
// body and docblock in lines that do not spell the term, removed no
645+
// mention, and left `data-action-routes.ts` untouched. No call site was
646+
// added. ⚠️ The dogfood shards skip on PRs and in the merge queue, so this
647+
// move was seen only by the hourly full run on `main`.
634648
controls: {
635649
'private register*Endpoints(': 16,
636650
'this.routeManager.register(': 63,
@@ -642,7 +656,7 @@ export const PROBE_FILE_CENSUS: readonly ProbeFileReading[] = [
642656
'registerPerItemRoute(': 8,
643657
'const registerPerItemRoute =': 1,
644658
'forwarder slice: this.routeManager.register(': 1,
645-
enforceAuth: 61,
659+
enforceAuth: 64,
646660
},
647661
note:
648662
'The single non-tripwire probe names ONE registrar of 16. The other 15 can never mint a key: ' +

0 commit comments

Comments
 (0)