fix(review-transport): dispatch continuations with app token

[seonghobae]

Goal

Harden the proposed Strix/Noema continuation adapter without overstating the unresolved cross-repository authorization boundary.

Exact root cause

Two separate defects were found:

1. The continuation exchange used jq -r '.value // empty' / '.token // empty' and only tested -z. Numeric OIDC values, object App tokens, and multiline App tokens exited zero; multiline content could inject extra $GITHUB_OUTPUT records.
2. Exchanging a consumer OIDC assertion at the existing endpoint does not prove that the returned token may dispatch into ContextualWisdomLab/.github. Retained protected evidence already exercises that sequence and ends with Resource not accessible by integration (HTTP 403): late-life-anxiety-reanalysis@34032cff52e8522db6ea0aad9f68ae0217e86ee3, local/supervisor-audit-20260912/current-ci/103571810868.log, blob cb91b0c0bfe1ff9001cab9e1675d97b00cfcef32, exchange/dispatch/failure at lines 141/158/173.

Repair in this Draft

• Preserve read-only consumer permissions plus id-token: write; do not restore the consumer github.token fallback.
• Parse the OIDC and App-token responses as exactly one JSON object whose credential is a nonempty, whitespace-free string.
• Fail closed before masking or writing output for typed, multi-object, malformed, or multiline credentials.
• Execute both real workflow shell blocks in RED/GREEN regression tests.
• Correct CHANGELOG, doctoring, and product-gap claims: this is a Draft adapter, not a completed transport repair.

Canonical owner dependency

The missing target/action-bound capability belongs to Noema: ContextualWisdomLab/noema#735. The owner-selected v1 shape is a synchronous POST /v1/continuation-dispatches broker: Noema validates exact OIDC/workflow/PR/head/base authority, performs one internally mapped central dispatch with a target-only installation token, and returns signed evidence without returning any GitHub credential. This consumer must replace its legacy exchange plus local gh api sequence only after Noema publishes an immutable versioned release. No PAT fallback, inherited central secret, source copy, consumer-visible broad installation token, or undocumented extension of the legacy endpoint is acceptable.

Exact verification

Exact published head: 48dbe4e7a080a0235cb0a244820c87232dada1f2

Exact published tree: a53818695d4f5ac141ff6173da165b8f47b68c25

• RED: both actual-shell regressions failed because malformed credentials exited zero.
• GREEN parser regressions include valid-response positive controls with exact mask/output assertions: 2 passed.
• Four affected workflow contract files: 120 passed, warnings fatal.
• Focused transport/security contracts: 29 passed, warnings fatal.
• Combined exact-tree suite on Python 3.14.7: 5307 passed, 7 skipped, warnings fatal.
• Production coverage: 18,729/18,729 statements and 7,642/7,642 branches (100%); production Docstrings 100%.
• Strix and Noema YAML parse with yaml.safe_load.
• git diff --check: clean.

Predecessor delta integration

This exact head completely carries the valid delta from #2510 while correcting its overclaim:

• both Strix and Noema consumer continuations use an exchanged credential only for the central dispatch and retain no consumer github.token fallback;
• actual workflow shells have positive valid-response controls and fail closed on missing, typed, multi-object, whitespace-bearing, or multiline credentials;
• CHANGELOG, doctoring, and docs/product-technical-gap-baseline.md retain the incident, ownership, acceptance gates, and current contextual-orchestrator#1349@832291c11da301e919d9dc20fda99f0847142dd8 Noema 429→93-second wait→central HTTP 403 recurrence;
• the earlier claim that the existing exchange proves central-dispatch authority is rejected by retained protected evidence, so Noema fix(deps): bump cryptography to 50.0.0 and constrain aiohttp >=3.14.3 in strix CI lock #735 remains the canonical owner prerequisite.

Fresh docs-bound verification after this carryover: 27 passed, 4 subtests passed with warnings fatal; git diff --check clean.

Stack and merge state

• Base/prerequisite: current combined successor fix(ci): integrate parser, security, response, and coverage gates #2530 at 5a91ce9f9c3e773aa1172f1055fd791ccde8fdaa.
• Exact ordinary merge parents are prior fix(review-transport): dispatch continuations with app token #2540 a92a201802d802867100c63b7da081e3bbf4861e and current fix(ci): integrate parser, security, response, and coverage gates #2530 5a91ce9f9c3e773aa1172f1055fd791ccde8fdaa; the latter carries the complete 3,709-line product-gap source restoration plus the canonical security, response-lifecycle, and coverage ancestry.
• Status: Draft / Proposed / BLOCKED on Noema fix(deps): bump cryptography to 50.0.0 and constrain aiohttp >=3.14.3 in strix CI lock #735/fix(ci): snapshot dependencies on default-branch pushes so dependency-review has a base #736 immutable release and consumer pin.
• Exact-head hosted Checks and qualifying independent review remain required after each source change.
• No merge, auto-merge, bypass, force update, destructive rebase, or PR closure is authorized.

GitHub permission-model consequence

GitHub's official repository-dispatch endpoint requires Contents: write for GitHub App installation and fine-grained tokens. Because GitHub exposes no narrower dispatch-only token permission, this Draft's consumer-visible App-token exchange cannot be the released least-privilege solution even if installation targeting is repaired. Noema #735 must instead broker the single allowlisted central dispatch server-side and return an exact-revision receipt without exposing a GitHub credential. After that immutable owner release, this consumer must replace—not merely parameterize or rename—the legacy /exchange_github_app_token step and regenerate exact-head tests and Checks.

2026-10-01 security-successor restack receipt

The prior exact-head Security Scan failed only on inherited PyO3 0.22.6. This head fixes that ownership error by ordinarily merging the current #2530 successor rather than copying security code. The current ancestry preserves PyO3 0.29.2, PyJWT 2.15.0, and urllib3 2.8.0 source/lock contracts. The only merge conflicts were CHANGELOG.md and docs/product-technical-gap-baseline.md; both resolutions retain the complete ordered factual sections from both parents. Independent staged-tree review found no Critical, Important, or Minor finding. The Noema broker remains unfinished, so this restack does not authorize Ready or merge.

2026-10-01 PyJWT security-successor restack receipt

The Security Scan finding on prior head 612d8e77… was inherited from the central Strix lock. Canonical owner #2531 repaired GHSA-42vr-xj54-vc7v at 9b4258de…; #2530 integrated it at f6a8bf5a…; this Draft now preserves both histories in ordinary two-parent commit 9e7f376d6d219570b3d042370f32ddd6dbdc44cc (tree deeac68f02bb73f6a664fac9fcc2e085781b5f79). The first-parent delta is exactly the six-file owner repair and the Noema broker prerequisite remains unresolved, so this is carryover—not Ready or merge authorization.

2026-10-01 control-character review repair

• P1 reproduction on predecessor 612d8e77…: the whitespace predicate accepted both NUL and BEL. Bash changed abc\\u0000def into abcdef and continued with status 0.
• Exact-head repair 37fb147a9dcb44a781c7cf7ca7f7a5ae4d29313e admits only [A-Za-z0-9._-]+ inside jq before raw output in all six Strix/Noema exchange fields.
• Actual-shell cases now inject NUL and BEL into both OIDC and App-token JSON values, require failure, forbid mask/output, and bind malformed OIDC to one curl only. Positive controls still require two curl calls and the exact mask/output records.
• Direct predicate replay is RED on the predecessor logic and GREEN on the exact alphabet. On current exact head a92a2018…, all 31 hosted Checks are terminal: 16 success and 15 intentionally skipped, with no failure or pending job. Qualifying approval remains absent and the Noema fix(deps): bump cryptography to 50.0.0 and constrain aiohttp >=3.14.3 in strix CI lock #735/fix(ci): snapshot dependencies on default-branch pushes so dependency-review has a base #736 immutable broker dependency remains unresolved, so this PR remains Draft / Proposed / merge HOLD.

2026-10-01 current security-owner evidence restack receipt

Exact head 83cf434823e61021951328fc9b65cd3d2c4bd8e4 (tree 9f0390420011827555dffe8e33aa9047abfadafe) is an ordinary two-parent merge of the reviewed control-character repair 37fb147a… and current #2530 5b3a76ea…. The first-parent file delta is exactly three owner documentation refinements; both workflow files and both NUL/BEL actual-shell regression files are byte-preserved. Compare evidence is ahead 4 / behind 0 from the prior #2540 head and ahead 9 / behind 0 from the current base. This restack preserves the Noema #735/#736 immutable-release HOLD and does not authorize Ready or merge.

2026-10-01 complete control-character evidence integration

Fast-forward child a92a201802d802867100c63b7da081e3bbf4861e (tree db123f2792c509202c28a4b9fa7c2cfdd7a51139) extends the reviewed NUL/BEL evidence without changing the six workflow predicates: it adds SOH to both continuation actual-shell cases, binds NUL/SOH rejection for the existing Strix metadata exchange, and aligns CHANGELOG, doctoring, and the product-gap baseline. Focused evidence is 52 affected tests and the combined warning-fatal suite is 5,300 passed, 5 skipped, and 40 subtests. Hosted exact-head Checks are 16 success / 15 skipped / 0 failure / 0 pending. This is source/evidence completion only; approval remains 0 and Noema #735/#736 remains an immutable-release prerequisite.

2026-10-01 current source-integrity owner refresh

Exact head 48dbe4e7a080a0235cb0a244820c87232dada1f2 (tree a53818695d4f5ac141ff6173da165b8f47b68c25) is an ordinary two-parent merge of prior #2540 a92a201802d802867100c63b7da081e3bbf4861e and current #2530 5a91ce9f9c3e773aa1172f1055fd791ccde8fdaa. The sole content conflict was the product/technical Gap baseline: the canonical restored 3,709-line owner artifact was retained and the two #2540 review-transport Gap sections were reapplied, producing 3,721 lines. The effective delta against current #2530 remains exactly the same nine reviewed #2540 files (434 additions, 12 deletions); the ref update was fast-forward and force=false.

Fresh exact-tree evidence: focused workflow/Gap contracts 58 passed; complete Python 3.14.7 warning-fatal suite 5,307 passed, 7 skipped; git diff --check GREEN. Exact-head Security 36790272276 and SAST 36790272400 are terminal-success; Draft-gated CodeQL 36790272294 is terminal-skipped and is not acceptance evidence. There are zero review threads and no qualifying APPROVED review. The Noema #735/#736 immutable broker release and consumer pin remain unresolved, so the PR stays Draft / Proposed / merge HOLD.

2026-10-01 latest security-owner restack (authoritative)

• Exact head: a4c1c7052d4a78bccc381f943d570ba00acd84f0; exact tree: b362e267910615aa617eb650d48cb53860415d4c.
• Ordinary two-parent merge preserves prior fix(review-transport): dispatch continuations with app token #2540 48dbe4e7a080a0235cb0a244820c87232dada1f2 and current canonical fix(ci): integrate parser, security, response, and coverage gates #2530 813f16fad7528b035d6ae4386cd176c9a67413c1; the branch ref advanced with force=false.
• Owner-to-leaf comparison is ahead 12 / behind 0 and mechanically mergeable. The effective delta is unchanged: exactly nine reviewed review-transport files (434 additions / 12 deletions).
• The only overlapping file, docs/product-technical-gap-baseline.md, was resolved from the complete current owner source. Both fix(review-transport): dispatch continuations with app token #2540 review-transport sections remain, alongside the owner's Maturin, LiteLLM, security, and source-integrity evidence.
• Exact-head Security 36804492171 and SAST 36804492204 are terminal GREEN; CodeQL 36804492185 is Draft-gated skipped and is not acceptance evidence. Noema fix(deps): bump cryptography to 50.0.0 and constrain aiohttp >=3.14.3 in strix CI lock #735/fix(ci): snapshot dependencies on default-branch pushes so dependency-review has a base #736 immutable release, consumer pin, Ready-admitted CodeQL/authenticated verdicts, and qualifying independent approval remain mandatory; no bypass, auto-merge, closure, or release is authorized.

2026-10-01 Noema owner exact-head gate refresh

• Canonical owner Noema#736 remains Ready and mechanically mergeable at exact head 81568910dccff168681b9b923e2c7667861b1063 on base 1204a075ac15b924e2f907804ba99c337d1a3ac7.
• Exact-head ci 36790870778, reviewer-ci 36790870754, Security 36790870914, and patch-validator-image 36790870794 are terminal GREEN; all eight review threads are resolved.
• Qualifying independent approval remains absent, so protected merge and immutable Noema release are not authorized. This consumer therefore remains Draft / Proposed and must not copy owner source, pin an open branch, or reactivate its legacy consumer-visible token exchange.

2026-10-01 current Maturin-owner restack

• Exact head: d8bc25753dcec4cb83b816835568c0e11a27f4e5; exact tree: 12f663b1b35c986555a7bba3763fa1067f534a5c.
• Ordinary merge parents are prior fix(review-transport): dispatch continuations with app token #2540 a4c1c7052d4a78bccc381f943d570ba00acd84f0 and current canonical fix(ci): integrate parser, security, response, and coverage gates #2530 dc54310c8c5ee6637274e7e82f5ea53d64ad91e6; the branch ref advanced with force=false.
• The sole conflict was docs/product-technical-gap-baseline.md. Resolution retains both the review-transport credential-character Gap and the owner Maturin response-lifecycle/stacked-quality Gap. The effective owner-to-leaf delta remains the same nine review-transport files, ahead 13 / behind 0 with merge base exactly current fix(ci): integrate parser, security, response, and coverage gates #2530.
• Fresh resolved-tree focus is 77 passed across Trusted uv/Maturin and the Noema/Strix actual-shell credential boundary; compileall, conflict-marker inspection, and git diff --check pass. Canonical owner run 36813245691 separately proves 5,314 passed, 5 skipped, 40 subtests, 100% statement/branch coverage, 100% production docstrings, and Python 3.10 compatibility on the exact inherited owner bytes.
• Exact-head fix(review-transport): dispatch continuations with app token #2540 Security 36814718513 and SAST 36814718496 are terminal GREEN; CodeQL 36814718724 is Draft-gated skipped and is not acceptance evidence. Review threads are 0 and qualifying APPROVED reviews are 0.
• Noema fix(ci): snapshot dependencies on default-branch pushes so dependency-review has a base #736 immutable release and consumer pin, Ready-admitted CodeQL/authenticated verdicts, and qualifying independent approval remain mandatory. This PR stays Draft / Proposed; no bypass, auto-merge, Force Push, closure, or predecessor-evidence promotion is authorized.

2026-10-01 current Noema owner evidence (authoritative)

• Canonical owner Noema#736 is Ready and mechanically mergeable at exact head 7487485a858f3d26827cabf153bdad3925ab577d, stacked on prerequisite Noema#737 exact head 5d9b4d00f1b692f3b911f4a56d834831d5b65bee.
• On fix(ci): snapshot dependencies on default-branch pushes so dependency-review has a base #736, exact-head ci 36834849920, reviewer-ci 36834849874, and patch-validator-image 36834849867 are terminal GREEN. A current-head Security run is absent because the stacked base is outside the protected-main Security ruleset; the earlier four-GREEN statement above is historical and is not current acceptance evidence.
• fix(ci): snapshot dependencies on default-branch pushes so dependency-review has a base #736 carries the three reviewed repairs for the empty POST /exchange section, duplicate TRD numbering, and route-specific attribution to /v1/continuation-dispatches. Review threads are 0, but qualifying APPROVED reviews remain 0.
• Prerequisite fix(coverage): materialize trusted uv lock dependencies #737 has terminal GREEN exact-head ci 36827780015, patch-validator-image 36827780026, Security Scan 36827779881, and reviewer-ci 36827780022; qualifying APPROVED reviews remain 0.
• Therefore neither ordinary protected integration nor an immutable Noema release is yet authorized. This consumer remains Draft / Proposed / merge HOLD and must not copy owner source, pin an open branch, or restore the legacy consumer-visible token exchange.

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Ordinary exact-head restack receipt for 056b3edfd513674068685affb1330684c1b659db (tree 50923de172a22dd8c1534e43d29b984af6b7de9b).

Parents are the prior #2540 head da1769e97047ecc26fbdd923e0630403eaf83815 and current prerequisite #2532 head 9d3ec75d6fbca20a6ac56de37408997fcafb01ea. The eight #2540 file blobs are byte-identical to the prior head; the merged tree adds only the reviewed five-file lifecycle repair from the new base. No force update or rebase was used.

Fresh combined-tree evidence (Python 3.12.14): Strix and Noema workflow YAML parsed; GITHUB_ACTIONS=true PYTHONPATH=. python -W error -m pytest -q completed 5165 passed, 11 skipped, 40 subtests passed; git diff --check is clean. The remote-created tree equals the independently validated local tree.

Merge remains HOLD: Security Scan and SAST are pending, CodeQL is queued, there are zero unresolved threads, and no qualifying independent APPROVED review exists. Ready is review admission only.

[seonghobae]

@coderabbitai review

Please review exact head 056b3edfd513674068685affb1330684c1b659db against stacked prerequisite 9d3ec75d6fbca20a6ac56de37408997fcafb01ea. Focus on the OIDC audience and subject binding, least-privilege job permissions, removal of the consumer-token fallback, fail-closed exchange/dispatch behavior, and whether the Strix/Noema contract tests bind both workflows without accepting a mutable or over-broad token. This manual request is required because automatic review skipped the non-default stacked base. Ready is review admission only; exact-head Checks and qualifying independent approval remain merge gates.

[coderabbitai]

⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[seonghobae]

Draft blocker — current head is not mergeable

Exact reviewed head: 056b3edfd513674068685affb1330684c1b659db (tree 50923de172a22dd8c1534e43d29b984af6b7de9b).

Two substantive defects remain:

1. Fail-open token parsing. Both new continuation exchange blocks use jq -r '.value // empty' / jq -r '.token // empty' and only test -z. Numeric, object, and multiline values therefore pass; a multiline GitHub App token can inject additional records into $GITHUB_OUTPUT. The repair must require one JSON object containing a nonempty, single-line whitespace-free string and must add executable malformed-response regressions for both Strix and Noema.
2. Known cross-repository authorization failure. The design exchanges a consumer OIDC token and then uses the returned App token to POST repos/ContextualWisdomLab/.github/dispatches. Retained protected evidence already records the same authority path failing with Resource not accessible by integration (HTTP 403): local/supervisor-audit-20260912/current-ci/103571810868.log, source ref 34032cff52e8522db6ea0aad9f68ae0217e86ee3, blob cb91b0c0bfe1ff9001cab9e1675d97b00cfcef32, exchange at line 141, central dispatch at line 158, failure at line 173. Protected doctoring also states this central-dispatch scope was unexercised and may be invalid (docs/doctoring/codeql-pr-private-consumer-read-permissions.md:21).

This PR remains Draft / Proposed. I am repairing the parser test-first here. The cross-repository capability belongs in the canonical Noema owner as a versioned, least-privilege contract and immutable release; consumer adoption must follow that release. No PAT fallback, bypass, or merge is justified.

[seonghobae]

Exact-head parser repair receipt for 0b4094b157b3dd73aa608f8d249fd18fa1d29174 (tree effae53a79ba3500dd204291614b2e6fda6684c9).

RED executed the actual Strix and Noema continuation exchange shell blocks: numeric OIDC, object App token, and multiline App token values were accepted by the parent and could reach $GITHUB_OUTPUT. GREEN requires exactly one JSON object with a nonempty whitespace-free string, before masking or output. Results: parser regressions 2 passed; four affected contract files 120 passed; full Python 3.12.14 warnings-fatal suite 5172 passed, 6 skipped, 40 subtests passed; YAML parsed and git diff --check is clean. The remote-created tree equals the locally validated tree.

This does not resolve central-dispatch authority. Retained protected evidence proves the same consumer exchange→central dispatch sequence fails HTTP 403. Canonical owner work is tracked at ContextualWisdomLab/noema#735 and requires a versioned immutable least-privilege release before consumer pin/adoption.

PR remains Draft / merge HOLD. Fresh exact-head Checks and qualifying independent review are required; Noema #735 is a substantive prerequisite. No bypass, force update, destructive rebase, PAT fallback, auto-merge, or closure was used.

[seonghobae]

Independent re-review found no Critical or Important defect and confirmed all malformed cases RED→GREEN. Its sole Minor finding was a vacuous-test risk: rejection-only assertions would also pass an always-failing exchange. Follow-up exact head d49ad6c693dbaafd8ec1b5f28c6be89a1a5eb569 (tree 27964517f04d89b4ffe5e549d4e4836db72d9938) adds valid-response controls to both actual-shell tests. Each now requires exit zero, exactly ::add-mask::valid-app, and exactly one token=valid-app output record before exercising the malformed matrix.

Fresh verification after the review repair: four affected files 120 passed with warnings fatal; full Python 3.12.14 suite 5172 passed, 6 skipped, 40 subtests passed; git diff --check clean. The Git data API tree equals the locally validated tree, and the branch moved by non-force fast-forward only.

Draft / merge HOLD remains unchanged: Noema #735 immutable owner release and consumer pin are substantive prerequisites; new exact-head Checks and qualifying protected review remain non-passing until terminal.

[seonghobae]

Exact-head COMMENT review for d49ad6c693dbaafd8ec1b5f28c6be89a1a5eb569 against stacked prerequisite 9d3ec75d6fbca20a6ac56de37408997fcafb01ea.

Independent diff review found no Critical or Important defect. The strict jq -ser contract rejects non-string, empty, whitespace-bearing, multiline, malformed, and multiple-object responses before credential use. Actual parent/current workflow-shell execution reproduced all three required exploit cases RED→GREEN. The review's sole Minor finding—rejection-only tests could pass an always-failing exchange—was repaired on this head with positive controls requiring successful valid exchange, the exact single mask line, and the exact single output record.

Fresh evidence: four affected test files 120 passed with warnings fatal; combined Python 3.12.14 suite 5172 passed, 6 skipped, 40 subtests passed; both YAML files parse; git diff --check passes. Documentation correctly retains the known HTTP 403 and Noema #735 immutable owner-release prerequisite.

This COMMENT is not approval. The PR is correctly Draft and is not merge-ready until Noema publishes and .github pins the versioned target/action-bound capability, hosted exact-head Checks are terminal GREEN, and protected review admission is satisfied.

[seonghobae]

Owner-boundary currentization for exact head d49ad6c693dbaafd8ec1b5f28c6be89a1a5eb569:

Noema #735 has selected a separate versioned broker contract, POST /v1/continuation-dispatches. GitHub requires Contents-write for repository dispatch, so returning any dispatch-capable installation token to this consumer would preserve the authority defect. The owner contract instead keeps the target-only token inside Noema, maps only the two allowlisted continuation actions, and returns a signed evidence receipt with no reusable credential.

The PR body now records that exact boundary. The current legacy exchange plus local gh api sequence remains Proposed and must not be promoted or adapted by inventing fields. Existing parser hardening remains valid delta, but merge stays HOLD until an immutable Noema release exists, this consumer pins it, and fresh exact-head Checks/review complete. No source push, rerun, or protection bypass was performed.

Owner design evidence: ContextualWisdomLab/noema#735 (comment)

[seonghobae]

Exact-head carryover receipt for f3896cecd099d85221cc28ed4f20d3dd103cc15c (tree 9a802beae20308fab72961c3b13ab5b2659d6788).

This head now preserves the current production recurrence from contextual-orchestrator#1349@832291c11da301e919d9dc20fda99f0847142dd8: Noema job 109737701886 emitted typed provider_capacity_unavailable after gateway HTTP 429; continuation job 109778469161 waited 93 seconds and failed central dispatch with HTTP 403.

Verified predecessor integration from #2510:

• both Strix and Noema continuation lanes retain the no-consumer-token contract;
• stricter actual-shell tests add valid-response controls and reject missing, typed, multi-object, whitespace-bearing, and multiline credentials;
• CHANGELOG, RCA, and product gap baseline preserve incident/owner/acceptance evidence while rejecting the unsupported claim that the existing exchange proves central dispatch authority;
• Noema fix(deps): bump cryptography to 50.0.0 and constrain aiohttp >=3.14.3 in strix CI lock #735 immutable least-privilege broker release remains the canonical prerequisite.

Fresh docs-bound verification: 27 passed, 4 subtests passed with warnings fatal; git diff --check clean. This remains Draft/Proposed and is not merge-authorized.

[seonghobae]

Canonical owner handoff: ContextualWisdomLab/noema#736 now carries the Proposed least-privilege continuation broker design and TDD plan at exact head 1f2465aac8b2ef16400b329eb050e17910d2a901, tree 2db47f3e7cebfe1ebe8c3645564b350a722a2bd5.

This is documentation-only and Draft. It does not unblock this consumer PR. Keep #2540 Draft until Noema implements and releases the versioned endpoint/schema, this PR pins that immutable release, and a real exact-head Noema/Strix continuation reaches the fixed central event and produces a fresh model verdict.

[seonghobae]

Pre-restack rationale: preserve canonical security owner

Current #2540 head f3896cecd099d85221cc28ed4f20d3dd103cc15c is based on #2532 9d3ec75d6fbca20a6ac56de37408997fcafb01ea. Exact-head Security Scan 36701119259, Trivy job 109869469856, fails on the inherited PyO3 0.22.6 fixture (GHSA-36hh-v3qg-5jq4, GHSA-chgr-c6px-7xpp). The valid patched fixture/source/contract is already owned by #2531 and preserved with #2532 in current combined successor #2530 ef014b9c877bd8b64733c630210ad155cde8a552.

Plan: ordinary two-parent merge current #2530 into current #2540, resolve only the two documentation collisions by retaining both factual deltas, run focused security/transport contracts and the full exact-tree suite, then update the existing #2540 branch with force=false and retarget its base to #2530. This is delta integration, not copied security code or predecessor disposal.

#2540 remains Draft/Proposed and blocked on the unfinished Noema continuation-dispatch owner release; the restack does not claim that dependency complete. No bypass, force push, destructive rebase, auto-merge, release, or closure.

[seonghobae]

Exact-head security-successor restack receipt

• HEAD: 612d8e77cf13eba84782a22587a72d3ffb4b6c6e
• tree: 0504e664754ab78cfee423d0725b833c15259b5e
• ordinary parents: prior fix(review-transport): dispatch continuations with app token #2540 f3896cecd099d85221cc28ed4f20d3dd103cc15c + current fix(ci): integrate parser, security, response, and coverage gates #2530 a2f73a4bc82ca783c114fa6e5020c511c948f0b7
• base retargeted to fix/full-suite-parser-locks-20260930@a2f73a4b…
• ref update: fast-forward, force=false

The previous Security Scan failed on inherited PyO3 0.22.6. This ordinary restack carries the canonical #2531/#2530 PyO3 0.29.2, PyJWT 2.14.0, and urllib3 2.8.0 repairs instead of copying them.

Fresh exact-tree evidence:

• focused transport/security contracts: 29 passed
• full warnings-as-errors: 5,296 passed, 5 skipped, 40 subtests
• production coverage: 18,729/18,729 statements and 7,642/7,642 branches (100%)
• production Docstrings: 100%
• 38 workflow YAML files parse; compileall and git diff --check pass
• independent staged-tree review: no Critical, Important, or Minor finding
• conflict resolution proved an ordered union of both factual CHANGELOG and gap-baseline sections; every other fix(ci): integrate parser, security, response, and coverage gates #2530 blob is preserved

This PR remains Draft / Proposed / HOLD. Noema #735/#736 has not produced an immutable broker release, and new exact-head hosted Checks/review are not yet merge authority. No merge, auto-merge, bypass, Force Push, rebase, release, or close was performed.

[seonghobae]

Exact-head review for 612d8e77cf13eba84782a22587a72d3ffb4b6c6e against stacked prerequisite a2f73a4bc82ca783c114fa6e5020c511c948f0b7.

[P1] Reject control characters before raw credential emission. Both new exchange blocks accept any nonempty string for which test("[[:space:]]") is false, then emit it with jq -r into Bash command substitution. A JSON credential containing NUL is therefore accepted by jq; Bash prints warning: command substitution: ignored null byte in input, deletes the byte, exits zero, and continues with a different credential. Minimal reproduction of the production predicate with {"token":"abc\\u0000def"} produced status=0 length=6 value=abcdef. On the OIDC leg the mutated value reaches the exchange Authorization header; on the App-token leg it reaches ::add-mask:: and $GITHUB_OUTPUT. This violates the stated fail-closed/exact credential boundary even though newline injection is blocked.

Acceptance: add actual-shell RED fixtures for NUL and at least one other C0 control character in both OIDC and App-token fields; reject them inside jq before -r output so no curl Authorization, mask, or output record is produced; preserve the current valid-response positive controls and the typed/multi-object/whitespace matrix. An exact token grammar is preferable where the two credential formats permit it; otherwise reject every control character explicitly.

Current-head hosted evidence is also non-passing: Security Scan 36741151937 failed in dependency-review job 109975641239 and OSV job 109975641271; CodeQL 36741151901 is skipped. SAST 36741151872 and Metadata 36741151940 succeeded, but they do not override the source finding or failed/skipped gates. The Noema #735/#736 immutable broker dependency remains unresolved. Keep Draft; no merge, auto-merge, bypass, or rerun is justified before a source change and fresh exact-head verification.

[seonghobae]

Inherited PyJWT finding repaired through ordinary successor integration at exact head 9e7f376d6d219570b3d042370f32ddd6dbdc44cc (tree deeac68f02bb73f6a664fac9fcc2e085781b5f79). Parents are prior #2540 612d8e77cf13eba84782a22587a72d3ffb4b6c6e and current #2530 f6a8bf5af862f9a23c0b85b7b78969cb77946c3d; both comparisons are ahead with behind 0. The first-parent delta is exactly the six-file PyJWT 2.15.0 canonical-owner repair. Fresh checks are running. The Noema #735/#736 release prerequisite remains unresolved, so the PR stays Draft / Proposed / merge HOLD.

[seonghobae]

P1 control-character finding repaired test-first at exact head 37fb147a9dcb44a781c7cf7ca7f7a5ae4d29313e (tree 70994c82f045dc383752d6f73bf2205c00b968fb).

• RED: predecessor whitespace-only jq predicate accepted NUL and BEL; Bash removed NUL and continued with mutated abcdef at status 0.
• GREEN: all six Strix/Noema OIDC/App-token parses now require ^[A-Za-z0-9._-]+$ before raw output.
• Actual-shell fixtures cover NUL and BEL in both fields, require nonzero exit, prohibit mask/output emission, and prove malformed OIDC never reaches the token-exchange curl; valid controls still require two curl calls.
• Delta is one ordinary fast-forward commit touching the two owner workflows, two tests, CHANGELOG/doctoring, and docs/product-technical-gap-baseline.md.

Fresh exact-head Checks are running. Noema #735/#736 is still an unreleased prerequisite, so Draft / merge HOLD remains; no force update, bypass, or manual rerun.

[seonghobae]

Exact restack receipt after current #2530 advancement

• exact head: 83cf434823e61021951328fc9b65cd3d2c4bd8e4
• exact tree: 9f0390420011827555dffe8e33aa9047abfadafe
• ordinary parents: reviewed control-character repair 37fb147a9dcb44a781c7cf7ca7f7a5ae4d29313e + current fix(ci): integrate parser, security, response, and coverage gates #2530 5b3a76ea71d7ae2fa9b1719f4f82df8d52e98082
• first-parent compare: ahead 4 / behind 0, with only three owner documentation files changed
• base compare: ahead 9 / behind 0; the two workflow files and two NUL/BEL actual-shell test files are preserved
• branch update: fast-forward with force=false

The exact ASCII credential grammar and NUL/BEL fail-closed repair remain intact. Noema #735/#736 is still unreleased, so the PR remains Draft / Proposed and merge is not authorized.

[seonghobae]

Exact-head integrated repair receipt

P1 is repaired on exact head a92a201802d802867100c63b7da081e3bbf4861e (tree db123f2792c509202c28a4b9fa7c2cfdd7a51139). The update is a non-force fast-forward from concurrent head 83cf434823e61021951328fc9b65cd3d2c4bd8e4; the connector created Git blobs/tree/commit and moved the ref with force=false after the ordinary local integration preserved both writers' intent.

• All six Strix/Noema OIDC/App-token parsing fields retain the exact [A-Za-z0-9._-]+ jq boundary before raw output.
• Actual continuation shells now cover NUL, SOH, and BEL in both credential legs. Invalid OIDC stops after one curl; no Authorization POST, mask, or output record is allowed.
• The existing Strix metadata exchange carries the same boundary and NUL/SOH executable fixtures.
• RED on predecessor 612d8e77…: NUL was deleted by Bash and the shell exited zero. GREEN: directly affected files 52 passed; four workflow-contract files 124 passed; PyJWT dependency contract 5 passed; full warning-fatal suite 5300 passed, 5 skipped, 40 subtests passed.
• Both YAML files parse with yaml.safe_load; git diff --check is clean.

This remains Draft / Proposed / merge HOLD. Fresh hosted exact-head Checks and a qualifying independent review are required, and Noema #735/#736 must still publish the immutable broker capability before the adapter can claim end-to-end transport completion. No rerun, bypass, merge, force update, or closure was performed.

[seonghobae]

Canonical owner repair snapshot:

• noema#736 exact head 1bd5fce7e8df5a3ecbda109071d9b2bbd7a5917b, tree 5228844956962bacad76cc2c572cb324acca96c0, base 1204a075ac15b924e2f907804ba99c337d1a3ac7; open, Ready-for-review, mergeable.
• Repaired expired-reservation same-transaction reuse, fixed-epoch test expiry, TypeScript narrowing, Worker expiry fixtures, and the 503 schema overlap (anyOf, with both real envelopes executed by contract tests).
• Exact-head CI 36790157474, reviewer-ci 36790157475, and Security Scan 36790157585: SUCCESS.
• patch-validator-image 36790157437: still running; not counted as GREEN.
• Review threads: 0 unresolved. Qualifying approvals: 0. GitHub Releases: 0.

Therefore the owner source is repaired but merge/release authority is not complete. .github#2540 remains correctly Draft and must not replace its legacy exchange/dispatch sequence or pin this contract until ordinary merge plus immutable Noema release publishes the receipt schema and key-id→SPKI artifact/digest.

[seonghobae]

Owner dependency refresh: Noema #736 is now at exact head 81568910dccff168681b9b923e2c7667861b1063 (tree cb2e60ceb4632ae381f245c24070ad000b1946bb). CI 36790870778, reviewer-ci 36790870754, and Security Scan 36790870914 are GREEN; patch-validator-image 36790870794 is still running and is not GREEN. All owner review threads are resolved, but APPROVED review count is 0 and Noema release count is 0. This consumer remains correctly Draft at 48dbe4e7a080a0235cb0a244820c87232dada1f2; do not replace the legacy exchange/local dispatch with owner source or an unreleased branch.

[seonghobae]

Base-move conflict repaired non-destructively at exact head a4c1c7052d4a78bccc381f943d570ba00acd84f0 (tree b362e267910615aa617eb650d48cb53860415d4c). This ordinary two-parent merge preserves prior leaf 48dbe4e7a080a0235cb0a244820c87232dada1f2 and current #2530 owner 813f16fad7528b035d6ae4386cd176c9a67413c1; the ref update used force=false.

The PR is mechanically mergeable, ahead 12 / behind 0, with the same nine-file effective delta (+434/-12). The complete current Gap baseline retains both review-transport sections and all current owner security evidence. Exact-head Security 36804492171 and SAST 36804492204 are terminal GREEN; CodeQL 36804492185 is Draft-gated skipped and is not acceptance evidence. Noema #735/#736 has no immutable broker release to pin, and no qualifying approval exists.