Repository navigation
Catalog: rebuild the API index after Connect (#156) and #157 - #159
Conversation
…ameters Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
💡 Codex Reviewhttps://github.com/SyberLabs/Flyspace/blob/6ca926f45da765fc0b73b1e41f58486b4d65c884/public/api-index.json#L1 The change description’s usable-API measurement is two low for both snapshots: the same predicate used by AGENTS.md reference: AGENTS.md:L108-L115 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Objective. Recount what the directory gives now that the compiler binds read-only Google sign-in (#156) and leaves out optional compound parameters on reads (#157), so search stops listing those APIs as blocked.
What changed.
public/api-index.jsononly, written bynpm run catalog:build(APIs.guru list, last modified 2025-08-18; every OpenAPI 3.x spec downloaded and compiled, 0 reused because the compiler fingerprint changed).What did not change. No code. The search label for a Google API still says "needs a key" rather than "needs sign-in" (the index's credential field has no sign-in value yet).
Tests run.
npx vitest run src/core/capabilities/apiIndex src/core/capabilities/providers: 3 files, 45 passed (index validation and the registry provider that searches it).Measurements (method:
npm run catalog:buildon 2026-10-12, before/after counted from the committed index)Remaining Google blockers, by the compiler's first error per API: 193 APIs have no read operation it can compile ('Signed-in operations are read-only…' is just the first refusal listed), 55 offer only scopes that can change data. Two concrete gaps found by compiling Calendar v3 and YouTube v3 by hand:
part, a required array query parameter, which the compiler refuses and the runtime cannot send yet.events.list: one untyped nested response property (Event.workingLocationProperties.homeOffice), which the compiler deliberately does not admit asany.Known failures.
microsoft.com:graphandgraph-betaexceed the 32 MB spec limit and stay unknown, as before.Claim ceiling. Measured compile counts. No Google operation has been called live (no OAuth client registered).
Architectural decisions introduced. None.
Evidence that could falsify it. Re-running
npm run catalog:buildon this commit and getting different counts with the same upstream list.Next permissible package. Required array query parameters (send as repeated
name=value,style: form, explode: true), which would unblock YouTube's list operations; then deciding whether an untyped nested output property may be dropped.🤖 Generated with Claude Code