Add scope coverage registry (SCOPES.md) — BUI-395#76
Merged
Conversation
Design for a single generated scope-coverage catalog in data-connectors that declares per-scope, per-tier (web/desktop) producibility. Kills the BUI-395 drift where "can the web flow produce scope X?" was hand-asserted in four disconnected places by collapsing them to one hand-declared input (web-capabilities.json) plus generated views (scope-coverage.json, SCOPES.md). unity-surfaces web-writable-scopes.ts becomes generated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Single human reference listing every scope, web (Data Pipe API) vs desktop (Playwright connector) fulfillment, and the exact connectors behind each. Resolves the BUI-395 "where do we document requested vs producible scopes" question with one manually maintained file. Deliberately no generator/codegen (web set changes rarely). Revises the design spec to match and drops the generation-based implementation plan. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Schema Health Check — Non-blocking inherited issues41/47 scopes consistent | 6 inherited Gateway gap(s) | no new blocking issues in this PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
SCOPES.md, a single hand-maintained reference listing every data scope, whether the web (ODL Data Pipe API) and/or desktop (Playwright connector) flow can fulfill it, and the exact connector(s) behind each scope.Also revises the design spec to match and removes the (now-obsolete) generation-based implementation plan.
Why
Resolves the open question on BUI-395: where should requested vs produced/readable scopes be documented?
The bug: a lab E2E requested
read:ads(→instagram.ads), but the web/light flow only producesinstagram.profile, so the Personal Server had noinstagram.adsdata → valid 404. There was no single place documenting which tier can fulfill which scope.Decision
Deliberately no generator / no codegen / no sync script — the web flow's set of fulfillable scopes changes infrequently, so a hand-maintained file is enough.
unity-surfaces'web-writable-scopes.tsis unchanged and kept consistent with the Web column by hand.Scope
SCOPES.md— the registry (47 scopes, 18 sources).docs/specs/2026-05-29-scope-coverage-catalog-design.md— rationale.🤖 Generated with Claude Code