Skip to content

Define and package the curated application face - #1

Merged
MiguelsPizza merged 5 commits into
mainfrom
alex/application-package-face
Aug 18, 2026
Merged

Define and package the curated application face#1
MiguelsPizza merged 5 commits into
mainfrom
alex/application-package-face

Conversation

@MiguelsPizza

@MiguelsPizza MiguelsPizza commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Why

Rook needs one small package contract for curated applications without forcing every provider into a universal runtime adapter. The package should own provider identity, model-facing types, client behavior, authoritative inputs, and browser proof; the extension should own Chrome authority, sandbox lifecycle, and transport routing.

This is the package-side dependency for rook#135, which pins the exact reviewed commit.

The generated Google surface continues to come from the Google API Discovery Service. The published entrypoint follows Node's package entry point contract with executable ESM and bundled declarations rather than TypeScript source under node_modules.

What changed

  • Define one Google Workspace application ID and generate its ApplicationsNamespace binding alongside the client types.
  • Export named authorization, transport, and workspace contracts for the installer boundary.
  • Export the curated card, searchable member index, related skills, auth requirements, requests, and native client from one root entrypoint.
  • Build deterministic browser ESM and .d.ts artifacts with Vite+ while retaining the source, skills, and authoritative Discovery inputs needed by Rook's immutable Git pin.
  • Validate the actual tarball through a clean install, Node runtime import, and minimal TypeScript consumer; fail when checked-in distribution artifacts drift.
  • Document temporary local linking for rapid extension development while keeping reviewed commit pins as final integration state.

Verification

  • vp run check
  • format, lint, TypeScript, and generated-source drift checks
  • 1 package contract test and 2 real-Chromium boundary tests
  • deterministic package build with no source maps
  • clean packed install, Node 24 runtime import, and NodeNext TypeScript consumer

Release scope

GraphQL and additional providers remain intentionally excluded. Changesets and npm trusted-publishing automation should land only when the @rook trusted publisher is configured.

Generate declarations, request metadata, and the searchable member index from the same pinned Discovery inputs so the typechecker, sandbox installer, and applications tool cannot drift. Keep native Drive transfer behavior and the existing auth owner behind the product package, and prove the final face through contract and real-browser tests.
Join each package's card, searchable members, and related skills behind one structural contract while leaving installers, authentication, and request semantics product-owned. Generate Google call prefixes and output descriptions so the host no longer has to reconstruct package metadata.
Keep shipped Google application facts in one package-owned contract: member effects are required, availability carries the native-files capability, and generated members derive from the shared face type. Narrow the generated transport metadata, validate the Drive files resource instead of casting it, and expose only the supported package root so host consumers cannot couple to generated internals.
Move the Google application identity, ambient execution binding, and installer boundary types into the package that owns them. This leaves Rook responsible only for Chrome authority and runtime orchestration.\n\nShip deterministic browser ESM and declarations because Git commit installs run with lifecycle scripts disabled. Validate the actual tarball through a clean Node import and TypeScript consumer so npm readiness is tested at the public boundary.
@MiguelsPizza MiguelsPizza changed the title Define the curated application package face Define and package the curated application face Aug 17, 2026
Google requires uploadType=multipart on the /upload URI. Binary files happened to survive the omitted mode, but text uploads could be created as empty Drive files. Set the required query parameter and exercise text bytes through the real Chromium multipart boundary.
@MiguelsPizza
MiguelsPizza merged commit 7690047 into main Aug 18, 2026
1 check passed
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