Repository navigation
docs: acceptance run against core main with C16 — 73/0/1, the unified grant route - #14
Merged
Merged
Conversation
… 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.
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
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.
Records the first acceptance run against a core that ships C16
(
byte5ai/omadia#824, epic #470) — the unifiedGET|PUT /api/v1/admin/runtime/installed/:id/grantsroute, the wizard'sPermissions step, in-process re-activation, and the B6 grant purge on uninstall.
scripts/acceptance-local.mjsCore
main@3df6dde8, pluginmain@a84d3fc(0.3.3, clean clone),@omadia/plugin-api1.7.0. The suite exits with the FAIL count; it exited0.The suite took the unified path, and says so
§3.15 went BLOCKED → PASS: uninstall now clears
plugin_sql_grantsandplugin_public_path_grants. The single remaining BLOCKED (§2.6 chat tools) isunchanged and honest — core exposes no tool-registry endpoint.
What the suite does not prove, and the probe that does
acceptance-local.mjsprobes for the route before its clean slate, where amissing 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=erroredwith the missing-grant reason →GET grantsreturning structured
missing[]→PUT grants→200,state=active, samepid before and after → uninstall → both tables
0→ reinstall → asks again.Two traps worth the paragraph
DATABASE_URLset, bootstrapauto-installs
knowledge-graph-neon, whoseactivate()doesCREATE EXTENSION vector. On stockpostgres:16boot aborts with a fatalthat names neither Postgres nor pgvector.
activewhile the plugin iserrored. The jobstate tracks the job, not
activate(). Automation should read the grantsroute, not the job.
Docs only — no code paths touched.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.