mirror of
https://github.com/razzant/ouroboros.git
synced 2026-10-03 20:27:56 +00:00
docs(ledger): owner closures for the F6-sync #2 forks, A.24 ratification, hub wave delivery
This commit is contained in:
parent
f89154406f
commit
196438c96c
1 changed files with 24 additions and 0 deletions
|
|
@ -5222,3 +5222,27 @@ all four `OUROBOROS_*` env vars on a fresh mktemp root, chromium+webkit from
|
|||
`test_ui_smoke_playwright.py` is a GIANT_PATHS entry and grew by 3 lines,
|
||||
which the path-set manifest does not measure). `git rev-parse HEAD`
|
||||
unchanged (bef13f5e) after every pytest.
|
||||
|
||||
## Owner closures for the F6-sync #2 forks and A.24 (2026-09-01, batch 10)
|
||||
|
||||
- **Q-F6b-1 CLOSED (owner 1A)**: host notes stay TYPED flags in result_meta
|
||||
(note kinds, no text); the 256-byte host reserve is not widened — the note
|
||||
text remains visible to the model in the composed result.
|
||||
- **Q-F6b-2 CLOSED (owner 2A)**: the owner-home read carve (В23=A) is
|
||||
re-affirmed as inherited from upstream — the credential-NAME gate applies to
|
||||
mutations only; reads/list/search rely on shape-based egress masking, with
|
||||
that residual disclosed.
|
||||
- **Q-F6b-3 CLOSED (owner 3A)**: A5 literal-argv disclosure is ratified —
|
||||
shell operators, redirects and env references inside a direct argv array are
|
||||
DISCLOSED notes, not refusals (model-facing capability widening accepted).
|
||||
- **A.24 RATIFIED (owner 4A)**: the composition-seam classification delta (a
|
||||
structured `{"ok": false}` behind an appended host note is a typed refusal,
|
||||
never a success) carries the owner-item id A.24.
|
||||
- **Hub wave (owner 5A of batch 9) DELIVERED**: razzant/OuroborosHub PR #52
|
||||
merged by razzant (merge commit 67dd5ca7): all 22 extension manifests declare
|
||||
`plugin_api: "2.0"`, catalog.json regenerated by the hub's own
|
||||
`scripts/build_catalog.py`. Backward compatibility verified on the live
|
||||
6.113.5 code (f3fbfdbb): `parse_skill_manifest_text` parses the new
|
||||
manifests, the field is preserved as unknown (`plugin_api=None`), `validate()`
|
||||
is empty, and 6.113.5 has no PluginAPI negotiation/admission consumer — old
|
||||
installs are unaffected beyond the ordinary content-hash bump.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue