Written before the release, per the release gate in RELEASE.md. 6.6.0 follows 6.5.0. This file opens the scope so that the release gate and the landing card can name the release being built. Its lines enter this file with the pull requests that carry them, as in 6.5.0.
Each pull request that changes the package and lands in 6.6.0 carries its own row here. Its title names the row,
[6.6.0 <Item>] type(scope): subject, so the landing card can count it.
| Item | Pull request | What it brings | Branch |
|---|---|---|---|
| PR499 | 499 | the readers and producers named in the known limitations of 6.5.0: trace structure paths, the Sigstore reader, eval-result v0.1 entries, the SD-JWT producers and emit_bundle read and write only what their own verifiers read, and every producer of an Ed25519 signature writes a signer's output only at 64 bytes; RESTRISIKO_660.md names the ML-DSA producers this rule does not cover |
fix/known-limits-650 |
| PR501 | 501 | the inspect and dev extras admit inspect_ai up to 0.3.288; INTEGRATIONS.md says what proofbundle verify checks of a re-signed receipt; CONTRIBUTING.md names the two uv variables the plugin tests keep |
docs/b32-inspect-ceiling-and-uv-names |
| PR502 | 502 | decision verify and outcome verify take the inputs of Sections 3.2 to 3.4 and 4 of draft-gruszka-audit-decision-receipts-07: action bytes, the case the relying party chooses with its approval record, a consumption state read only, the expected executor, effect bytes and the bound decision with its evaluation time; the draft's stricter field rules stay a named limit in docs/NON_CLAIMS.md | fix/660-b4-review-4 |
| PR503 | 503 | a Trust Pack key attests only the executor.id values its executorIds name: an outcome under another identifier is not trusted (EXECUTOR_ID_NOT_ATTESTED), a key entry without executorIds binds no identifier and says so (EXECUTOR_ID_NOT_BOUND), and the schema states the bounds the validator holds on keys, keyIds and executorIds |
fix/660-executor-id-bound-by-trust-pack |
| PR505 | 505 | the command line refuses an abbreviated long option at every subcommand (allow_abbrev=False on the parser and its 40 subparsers at that merge, 42 at the release head with pull request 506) instead of reading it as the option it prefixes; CROSS_IMPLEMENTATION_REPORT.md names the new difference to pb_verify_rs as R3 |
fix/660-b23-refuse-abbreviated-options |
| PR506 | 506 | proofbundle scitt match, EXPERIMENTAL: the reader of draft-gruszka-scitt-statement-identification-03 reports ref_usable, match and is_scitt of Section 6 for a reference and a candidate Signed Statement under the scheme the caller names (ToBeSigned or WholeBytes), and a signature axis under the Ed25519 profile; input the strict CBOR reader does not read gets no verdict |
feat/660-scitt-match-reader |
| PR492 | 492 | example only: examples/vcon_ai_agent_receipts/real_session/ builds one unsigned vCon from a recorded session behind the guard and the two decision receipts the guard signed in it, and checks each receipt with proofbundle decision verify --strict and its binding to the session, to the call it names and to the escalated comment; no change to the package |
docs/vcon-ai-agent-real-session |
| PR507 | 507 | the decision receipt contract says what the verifier does on six points: the serialization of the eval-result in-toto export, the empty findings list, freshness_ok over authenticated bytes only, the order of the exit codes of decision verify, the result field list, and the subject binding of build_decision_statement; comments, docstrings and docs/predicates/trust-pack.md cite the published -05 of the audit draft where its section holds the rule, and the fraction rule names a coming revision; no behaviour changes |
docs/660-contract-texts-against-the-code |
| PR509 | 509 | documentation only: docs/RELATED_WORK.md names pedro and Santa under execution-level enforcement and telemetry, each by what its README states; the release gate in RELEASE.md names the public interface as the four surfaces of COMPATIBILITY.md and says that a fix rejecting input the specification already called invalid, or correcting a time verdict to what the specification states, may ship in a PATCH and says so explicitly, and COMPATIBILITY.md names the corrected time verdict beside the tightened check, as in 6.2.1 |
docs/660-related-work-enforcement-and-patch-rule |
| PR511 | 511 | decision verify fails an attached --with-related target that does not verify, also where no edge of the receipt names it, with lineage_ok false, the error relation:target_verification_failed and exit 2 unless a check decided before gives its own exit; a --related-pub without its target is refused with exit 2 |
fix/660-b22-ok-only-when-every-binding-holds |
| PR512 | 512 | documentation only: twenty-five pages open for people, twenty-two with a short introduction and the three pages of the plugin with how to use it, folding the former text below with its anchors kept, and docs/INSPECT_HAPPY_PATH.md names the inspect_ai ceiling of main, held by a test against pyproject.toml; no behaviour changes |
docs/660-entry-texts-for-people |
| PR515 | 515 | five containers refuse a member they do not name: a pre-tag receipt with a member outside its signed set is refused and a rejected receipt beside a valid one leaves the commit not verified, the release gate and the third-party verifier read the receipt folder and each receipt file one way, verify_evidence_pack judges a pack against the closed member set of its own pack version, measure_vector_set refuses a case directory the manifest does not name, C10.4 passes only on the two files of the self-receipt, and a build identity is the closed set of files its RECORD names, or every file of a source tree but the bytecode cache |
fix/660-containers-refuse-foreign-members |
| PR519 | 519 | the four findings of the deep gate at d8881edc, each fixed as a class: dsse.sign_envelope signs only an envelope that verify_envelope reads within its budget, the Sigstore reader reads the dates and names of every trusted-root certificate inside its boundary, an attached --with-related receipt counts as verified only when its predicate passes the structure check of its type and the rule of B22 holds in outcome verify and relation-statement verify as well, and all three commands refuse a --related-pub without its target; pb_verify_rs applies the rule of B22 as well, and the structure check of an attachment stays a named difference, R4 |
fix/660-deep-gate-i1-classes |
| PR521 | 521 | the six findings of the deep gate at c3472f6f, each fixed as a class with its neighbours: an attached receipt of one of our types without a predicate fails the requested lineage check, decision verify, outcome verify and relation-statement verify print the sentence of a verified receipt only when they exit 0, sign_trust_pack, issue_status_list_token and issue_enclave_attestation sign only what their verifiers read within the budget and sign_trust_pack refuses a hybrid signer, the certificate readers of verify_sigstore_bundle share one set of read errors, measure_vector_set leaves no directory of the corpus out, and pb_verify_rs refuses a primary statement that is not RFC 8785 canonical and a relation statement without its required members; the 6.6.0 heading was dated 2026-11-15 there, and PR528 moves it to 2026-11-16 |
fix/660-deep-gate-l6-classes |
| PR523 | 523 | the two findings of the deep gate at c71eeb12 that came with 6.6.0: the preflights of issue_status_list_token, issue_enclave_attestation and dsse.sign_envelope judge only the budget their verifiers read under, also where a string holds a lone surrogate, and leave questions of form to the verifier, and pb_verify_rs refuses a --related-pub without its target in both relation commands, with the reason Python gives; the three findings at c71eeb12 that were present at v6.5.0 as well stay open in RESTRISIKO_660.md |
fix/660-deep-gate-c4-two-new |
| PR524 | 524 | the finding of the deep gate at 41959070 on the signing key file: save_signer writes the seed into a new file with mode 0600 and follows no link at its path, every --new-key option refuses a path that exists, and its overwrite counts only as an exact bool; the neighbour in the key tool of the guard plugin stays open in RESTRISIKO_660.md until the plugin pins 6.6.0 |
fix/660-save-signer-mode-link-overwrite |
| PR525 | 525 | documentation only: the findings of the deep gate at 41959070 in RESTRISIKO_660.md, each confirmed P2 and P3 finding with its file and lines, its stage and the heads where it shows, and the coverage of the run as the owner judged it |
docs/660-residual-deep-gate-k0 |
| PR527 | 527 | documentation and release tooling only: six statements of the 6.6.0 texts that a counter-reading found too wide or out of date, among them the two open forms of --new-key in SECURITY.md and the sentence on R620-ABA-1 beside the register statement in audit_artifacts/660/README.md; the baseline limit of the mutation run at 10800 s, as run 5 of 6.5.0 set it at run time; and the gate-log fixture repositories without git's background maintenance; no module of the installed package changes |
docs/660-texts-and-mutation-limit |
| PR528 | 528 | documentation and release tooling only: the 6.6.0 heading of the CHANGELOG is dated 2026-11-16, the day the owner chose for the tag, and the release notes are rendered again from their source; no module of the installed package changes | docs/660-date-16-november |
| R1 | the preparation pull request | the version bump to 6.6.0, its CHANGELOG section, residual-risk record and audit page, the Out section of this file, the release notes rendered from their source, and signing the findings register for 6.6.0. R1 is not complete until that signature exists. | chore/prepare-6.6.0 |
Out means that an item is not an independent blocker for 6.6.0; it does not prove absence of outward effects. The scope files of earlier releases keep their rows and their recorded state; this file does not reopen them.
Measured over the 21 first-parent merges of v6.5.0..82411560 with git diff --name-only against each first parent:
9 change src/ or pyproject.toml (pull requests 499, 501, 502, 503, 505, 506, 507, 511 and 515), and each carries
its row under In. 12 change neither. Three of them carry a row under In as documentation or an example (492, 509 and
512); the other nine stand below. By the owner choice of 2026-11-12, main closes for 6.6.0 with pull request 497, and
until the tag only what the release plan names lands.
Each row is release evidence, internal tooling, an interoperability corpus or a test of this repository, with no change
to the installed package. Pull request 493 changes only files under audit_artifacts/, which MANIFEST.in prunes.
Pull requests 500 and 504 add case corpora under interop/, which no line of MANIFEST.in names, and each adds a
test. Pull request 508 changes one test. Pull request 497 changes tests/_plugin_env.py and six test modules, which
the sdist carries, and no module of the installed package; it carries the commit of pull request 488, which was closed
without a merge. Pull request 498 changes scripts/audit_candidate_matrix.py, scripts/gate_qualification_harness.py
and scripts/mutation_check.py, which the sdist carries, two tests and CHANGELOG.md, and no module of the installed
package; its CHANGELOG entry stands under Changed.
| Item | Pull request | Work retained | State |
|---|---|---|---|
| PR493 | 493 | the release evidence of 6.5.0: the pre-tag receipt, the fuzz soak record and the Rust differential matrix, under audit_artifacts/ |
Landed as ac4129f7 |
| PR497 | 497 | a plugin test reads no file or setting of the person who runs it: HOME points at an empty folder of the module, uv keeps the caller's cache, each plugin module runs under umask 022, and the children of a plugin test keep VIRTUAL_ENV (the commit of pull request 488) |
Landed as 82411560 |
| PR498 | 498 | the audit matrix reports the full 24-hour soak, row C6.3, as informative, as decided for the release on 2026-09-08 | Landed as 9bf5e9aa |
| PR500 | 500 | starter cases for draft-gruszka-audit-decision-receipts-07 under interop/audit-decision-receipts-07/, with a runner that reads an answer strictly, and a test |
Landed as d865f043 |
| PR504 | 504 | the cases of draft-gruszka-scitt-statement-identification-03 under interop/scitt-statement-identification-03/ with a checker, and a test |
Landed as e6807687 |
| PR508 | 508 | the test of a register with a member named twice builds the register once per case, so it no longer fails at a second boundary of the clock | Landed as 5bdf225d |
The plugins under plugins/ are released on their own; MANIFEST.in prunes plugins/. Pull request 494 also
changes .github/workflows/ci.yml, four tests and this file, which it opened. Pull request 496 changes README.md,
which is the long description of the package on PyPI (pyproject.toml, readme), and a test. Pull request 510
changes a test.
| Item | Pull request | What it brings | State |
|---|---|---|---|
| PR494 | 494 | the plugins pin proofbundle==6.5.0 in the gate and the MCP server, and this scope file opens as not started after the tag v6.5.0 |
Landed as 520cdc3d |
| PR496 | 496 | the README shows the agent plugins, and the plugin README opens for people | Landed as 6b63cda8 |
| PR510 | 510 | the release reader of the guard reads every spelling git takes for a door | Landed as db60f845 |