Skip to content

Catalog: rebuild the API index after #160 and #161 - #163

Merged
sykosyber merged 1 commit into
mainfrom
wp/omni/catalog-refresh-2
Oct 13, 2026
Merged

sykosyber merged 1 commit into
mainfrom
wp/omni/catalog-refresh-2

Conversation

@sykosyber

Copy link
Copy Markdown
Member

Objective. Recount the directory now that the compiler sends list-valued query parameters on reads (#160) and types untyped nested response fields as any (#161).

What changed. public/api-index.json only, from npm run catalog:build (APIs.guru list last modified 2025-08-18; all 1,521 OpenAPI 3.x specs downloaded and compiled, none reused because the compiler fingerprint changed).

What did not change. No code. Search still labels a Google API "needs a key" rather than "needs sign-in".

Tests run. npx vitest run src/core/capabilities/apiIndex src/core/capabilities/providers: 3 files, 45 passed.

Measurements (method: npm run catalog:build on 2026-10-12; counted from the committed index before and after)

before (#159) after
APIs with at least one usable operation 479 552
usable operations 9,009 10,137
Google APIs usable 7 74
usable and keyless 147 179
usable, needing a key or sign-in 299 (+33 partial) 335 (+38 partial)

Examples: Calendar 10 operations, YouTube 18, Drive 19, Gmail 23, Tasks 4. Books still compiles nothing: its read operations offer only a scope that can change data. Note for the owner: Google classes Gmail's read-only scope as restricted, so a production app needs Google's verification before people outside the test-user list can grant it.

Known failures. microsoft.com:graph and graph-beta exceed the 32 MB spec limit, 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. A rerun of npm run catalog:build on this commit producing different counts from the same upstream list.

Next permissible package. A "needs sign-in" credential label in search, so Google APIs are not shown as needing a key.

🤖 Generated with Claude Code

…fields

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sykosyber
sykosyber enabled auto-merge October 13, 2026 03:12
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-13T03:21:21.240651Z fb4e7fb PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@sykosyber
sykosyber merged commit 321fd02 into main Oct 13, 2026
4 checks passed
@sykosyber
sykosyber deleted the wp/omni/catalog-refresh-2 branch October 13, 2026 03:15
@chatgpt-codex-connector

Copy link
Copy Markdown

💡 Codex Review

https://github.com/SyberLabs/Flyspace/blob/fb4e7fbdea32d997c91c95d1e2719bb7660e62a9/public/api-index.json#L1
P2 Badge Stamp the index with the actual compiler fingerprint

The committed compiler value is 761bacff491c3bdc549a31948c8d348a, but compilerFingerprint() at this revision hashes the 41 direct non-test modules in src/core/capabilities/ to d1662cecb7772232862afbfbe02bfdc4. Since previousCounts() only reuses entries when this stamp matches the current compiler, the next npm run catalog:build will treat every count as stale and re-fetch/recompile all 1,521 OpenAPI specs even when neither the directory nor compiler changed; regenerate the artifact with the matching fingerprint.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

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".

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