superbee 0.4.4-pre.5 → 0.4.4-pre.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/superbee.mjs +669 -447
- package/package.json +1 -1
- package/references/author-an-integration.md +9 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "superbee",
|
|
3
|
-
"version": "0.4.4-pre.
|
|
3
|
+
"version": "0.4.4-pre.6",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Agent-facing Superbee CLI for reading and writing local OKF knowledge bundles: context notes, docs, cross-links, and live bundle Views.",
|
|
6
6
|
"keywords": [
|
|
@@ -81,6 +81,15 @@ and findings for every run. A recipe's definitions-only directory and recorded f
|
|
|
81
81
|
separate. Expected values are compared exactly; missing expectation keys, changed receipts, unused
|
|
82
82
|
recorded exchanges, unscripted requests and failed core invariants fail the command.
|
|
83
83
|
|
|
84
|
+
For a source with an explicit `request.read_policy`, the fixture author may supply the optional
|
|
85
|
+
top-level `readPolicyApproval` object: `{"contract":1,"digest":"sha256:<reviewed policy digest>"}`.
|
|
86
|
+
Obtain that digest from Core's public `inspectSourceReadPolicy(connector, boundFeed)` for the exact
|
|
87
|
+
reviewed declaration and bound Feed, then record it explicitly. The CLI forwards this fixture data
|
|
88
|
+
to the public Core harness; it never calculates or grants approval automatically. Core refuses
|
|
89
|
+
missing, stale or nonmatching approval before provider requests. The object permits only `contract`
|
|
90
|
+
and `digest`; legacy fixtures without an explicit read policy need no approval. This assertion
|
|
91
|
+
applies only to recorded testing: it grants no live feed binding consent, credential or transport.
|
|
92
|
+
|
|
84
93
|
Each exchange records the method and URL expected by the public harness and a response (`status`,
|
|
85
94
|
optional headers and body), `{ "fail": true }`, or `{ "hang": true }`. Runs may specify `mode`, `at`,
|
|
86
95
|
`edits` and a bounded engine `budget`. Fixture records can include hostile URLs and other attack
|