Skip to content

docs: acceptance run against core main with C16 — 73/0/1, the unified grant route - #14

Merged
Weegy merged 1 commit into
mainfrom
docs/acceptance-c16-0821c
Aug 21, 2026
Merged

Weegy merged 1 commit into
mainfrom
docs/acceptance-c16-0821c

Conversation

@Weegy

@Weegy Weegy commented Aug 21, 2026 •

Copy link
Copy Markdown
Contributor

Records the first acceptance run against a core that ships C16
(byte5ai/omadia#824, epic #470) — the unified
GET|PUT /api/v1/admin/runtime/installed/:id/grants route, the wizard's
Permissions step, in-process re-activation, and the B6 grant purge on uninstall.

Suite PASS FAIL BLOCKED Rows
scripts/acceptance-local.mjs 73 0 1 74
C16 grant-consent "Skip" probe 15 0 0 15

Core main @ 3df6dde8, plugin main @ a84d3fc (0.3.3, clean clone),
@omadia/plugin-api 1.7.0. The suite exits with the FAIL count; it exited 0.

The suite took the unified path, and says so

PASS  both grants (C16 unified PUT)              sql=true, 3 public paths, state=active
PASS  grant takes effect in-process (no restart) state=active straight out of the PUT

§3.15 went BLOCKED → PASS: uninstall now clears plugin_sql_grants and
plugin_public_path_grants. The single remaining BLOCKED (§2.6 chat tools) is
unchanged and honest — core exposes no tool-registry endpoint.

What the suite does not prove, and the probe that does

acceptance-local.mjs probes for the route before its clean slate, where a
missing route and a not-installed plugin both answer 404. It refuses to read
that as "no C16" and keeps the pre-C16 ordering — so the unified PUT lands on a
plugin whose SQL grant is already on record. That proves the route works, not
that it alone repairs an ungranted plugin.

The Skip flow was therefore walked separately and is quoted verbatim in the doc:
install → Skip → state=errored with the missing-grant reason → GET grants
returning structured missing[] → PUT grants → 200, state=active, same
pid before and after
→ uninstall → both tables 0 → reinstall → asks again.

Two traps worth the paragraph

  • This core needs a pgvector image. With DATABASE_URL set, bootstrap
    auto-installs knowledge-graph-neon, whose activate() does
    CREATE EXTENSION vector. On stock postgres:16 boot aborts with a fatal
    that names neither Postgres nor pgvector.
  • The install job reports active while the plugin is errored. The job
    state tracks the job, not activate(). Automation should read the grants
    route, not the job.

Docs only — no code paths touched.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

… grant route

First run against a core that ships C16 (byte5ai/omadia#824). The suite takes
the unified PUT /api/v1/admin/runtime/installed/:id/grants and says so; the
uninstall grant purge (B6) turned the §3.15 BLOCKED of 2026-08-21b into a PASS.

Records a second, separate probe for the flow the main harness cannot reach:
its route pre-probe runs before the clean slate, where a 404 is ambiguous, so it
keeps the pre-C16 ordering and the unified PUT lands on an already-granted
plugin. Pressing Skip -> errored -> GET grants missing[] -> PUT -> active with
no restart -> uninstall clears both tables -> reinstall asks again was walked
on its own and is quoted verbatim.

Also notes two traps: this core needs a pgvector image (stock postgres:16 aborts
boot with a message naming neither), and the install job reports active while
the plugin is errored.
@Weegy
Weegy merged commit 5f82b60 into main Aug 21, 2026
3 checks 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