You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6c9f359
Browse filesBrowse the repository at this point in the historyBrowse files
fix(rest): the export audit event carries the query as read under readQuery, and two test files meet their gates
The rest slot census (rest-server-canonical-query-ast.test.ts) counts every
`query:` line in data-action-routes.ts as a server-built QueryAST slot. The
export audit event's `query` member (its type and its literal) read as two
new slots, 8 against the pinned 6, though neither reaches the engine. The
member is now `readQuery` in the door, the plugin-audit writer and their
tests; the census is back to 6 with nothing re-pinned.
rest-api-plugin-slot-lookups.test.ts, edited by this branch, reaches
`@objectstack/objectql` through two route handlers' dynamic imports; a
module-top side-effect import pays that load during collection
(check:test-source-alias, "The source reach").
The export of an object name the registry does not know, past an export
gate that admitted it, is pinned as built: one failed event, 404
OBJECT_NOT_FOUND.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01L9qibwj6uu1L1hVh8hXHro
it('an export of an object name the registry does not know, past an export gate that let it through, hands ONE failed event (404 OBJECT_NOT_FOUND)',async()=>{
873
+
// Pinned as built, for the review to judge: the gates passed and the read
874
+
// began, so by the door's one rule this is an export that failed, not a
875
+
// refusal. Only a caller the export gate admits for that name reaches it.
0 commit comments