|
All checks were successful
CI / Import/export fidelity gate (push) Successful in 58s
CI / Build container images (push) Has been skipped
CI / Lint, typecheck, test (push) Successful in 3m2s
CD / Build and push images (push) Successful in 3m16s
CI / Auth e2e pack (push) Successful in 4m13s
CD / Smoke tests against Test (push) Successful in 1m6s
CD / Deploy to Test (push) Successful in 9s
CD / Promote to Int (push) Successful in 9s
CI / Warm action cache (push) Successful in 10s
Viewer-scoped data API behind /api/v1/plugin/, backing the SDK's
readCurrentPage and readPond capabilities:
- api: PluginApiController with GET plugin/ponds/:id/pages (listPages),
plugin/pages/:id/{outline,content,meta}. Each reuses the existing
@RequiresPondRole/@RequiresPagePermission guards and PagesService — no
parallel permission logic — so a plugin sees exactly what its viewer
could. New PagesService.outline/meta read the content cache.
- web: host-capabilities builds the host implementations from a per-
surface context (the host holds the current page/pond ids; a plugin can
only ask about "the current page" or "this pond"). Wired into the
sandbox host and PluginFrame; ui.openPage/toast route to host callbacks.
- shared: PluginPageSummary/Meta/Content response types.
- tests: api db test proves a label-restricted reader gets a filtered
listPages and 404s on the hidden page, non-members are hidden (404),
anonymous is rejected (401); web unit test pins the endpoint mapping,
id-encoding, and missing-context rejection.
readBlock/blockData land with the plugin_block node in #76 (block
addressing does not exist in the schema yet).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EwZ4jR4KFAPvpjWevfUGX1
|
||
|---|---|---|
| .. | ||
| plugin-sdk | ||
| shared | ||