[rmcdaniel]

The Rust binary recognizes workflow:list but returns the unavailable-command error. Implement one visibility page in the selected namespace, with PHP-compatible filters/page-size casts, table/JSON/JSONL output, namespace enrichment, preserved Server fields/cursors and the existing compatibility preflight.

Use the pinned public SDK 4.12.0 raw-request API for one HTTP attempt with its existing base path, TLS transport, namespace and token. Preserve protocol headers, validate canonical status filters and apply the PHP response-contract validation/projection. HTTP rejections retain their error/exit categories. No second HTTP client, retry or page-following loop is added.

Extract the existing doctor literal-display helper unchanged and reuse it for list rows and this command's warnings/human errors. Remote values cannot introduce formatter markup or terminal layout; machine JSON retains original values. Other commands retain their accepted formatting behavior.

The unchanged implementation has passed local Rust 1.86 formatting, Clippy, 140 ordinary Rust tests and two PHP differential suites, including 278 workflow-response cases and eight focused command controls. All 22 new mock cases match current PHP source. Original debug/release parity failures remain in history; the corrected implementation has 381/392 matches, eleven narrowly documented differences and zero unexpected. The sole new published-reference difference is the accepted PHP main canonical-filter JSON error versus pinned PHP 2.3.5 stderr, with exact envelope/exit/zero-request controls. Dependency, published-reference and Server pins remain unchanged.

Ref #72. Normally refreshed after accepted #108/#107 main: current head 3c66f588914665d27213b1f3fec7eeb96d283495, tree 690c2ad6e567426b3316eab7702e6404c7f36bdd, base e6c02e09e4be3becd94897b95fac19b4f5d31027. All sixteen reviewed implementation paths and all four incoming main paths preserve their reviewed blobs. Local whitespace, boundary and secret/private-location checks pass; fresh hosted qualification now passes all 26 checks, with five native builds, debug/release parity 381/392 (eleven documented differences, zero unexpected), PHP 8.2–8.5, PHAR/reproducibility, CodeQL and Sonar zero unresolved findings. Independent exact-pair review remains required; old-base SOURCE PASS does not automatically carry.

This adds one executable command; candidate coverage is 19/86, not stable 2.5 readiness. TLS opt-out support, Intel installer source, other handlers, live Server qualification and release/publication gates remain outside the slice. No public CLI or live Server was executed locally; comparisons used source and disposable loopback fixtures.

[rmcdaniel]

Source successor is 771552a69ca60b59d649a7d4eccc96c92c80d165 / tree 66f8dbae43811fb51f154056dd261e06e1afb2aa, over first source 48c397c and unchanged base 2592865. The original Build 41951864137 and release dry run 41951864164 remain failed: both report 380/392 matching, ten pre-existing intentional differences and two unexpected differences. All five native builds, PHP suites, PHAR/reproducibility, CodeQL and provider analysis passed, but do not override those failures.

The normal published-reference comparison found two distinct boundaries:

1. Unconditionally escaping shared human errors changed the existing ANSI reset/reapply sequence around the trusted <name> placeholder in env:show. Literal rendering is now scoped to this new workflow command, including its compatibility warning. Existing commands keep their accepted rendering, and a focused renderer regression asserts the placeholder boundaries. No exception is added for this case.
2. Published reference PHP 2.3.5 writes canonical status-filter errors to stderr even with --json. Accepted PHP main emits the structured JSON envelope under Expose command keys with safe human output and exact JSON values #61. This port retains that accepted machine contract: exit 2, exact error/command/namespace/recommendation envelope, empty stderr and zero list requests are explicitly asserted by the command test. Only this named parity case records its four changed output fields; exit status and all other comparison fields stay enforced. The published reference pin is unchanged. This is the one intentional addition to the existing ten differences, not a blanket error waiver.

Local successor evidence: fmt/Clippy with warnings denied, 140 normal Rust tests, and both PHP differential suites pass; the response suite retains all 278 cases. All 22 workflow cases still match current PHP source exactly. The additional ANSI check against current PHP source differs because PHP main already escaped that legacy placeholder, while this slice deliberately preserves the previously accepted Rust/published-reference behavior for unrelated commands; the new focused Rust control binds that boundary. No unrelated PHP/Rust error migration or reference replacement is included.

Changed-file secret/private-location, JSON, whitespace and public-boundary checks pass. Fresh exact-successor ordinary Build, native release parity and provider results are required before independent review. No manual retry/dispatch, public CLI execution locally, live Server, release or runtime experiment was performed.

[rmcdaniel]

Exact source 771552a69ca60b59d649a7d4eccc96c92c80d165, tree 66f8dbae43811fb51f154056dd261e06e1afb2aa, base accepted main 2592865dbee812f21195d93fa55188037a0a79cf, is CLEAN with 26/26 terminal successful checks and no failed/skipped/pending checks. Build 41953066797, five-platform release dry run 41953066765 and Sonar 41953066751 bind this exact head. CodeQL, both boundary scans, target qualification and independent same-head SonarCloud pass; provider gate OK and zero unresolved findings.

Both ordinary/debug and release-binary published-reference comparisons report 381/392 matches, eleven documented differences, zero unexpected. The existing ten differences remain; the only addition is the named legacy 2.3.5 invalid-filter JSON case described in the successor proof. All five native builds pass. PHP 8.2–8.5 each pass 987 cases / 18,420 assertions with the existing one skip and eleven deprecations. PHAR smoke and bit-identical reproducibility pass. The original failed debug/release runs remain failed and preserved.

Local exact-product evidence includes 140 normal Rust tests, both PHP differential suites including 278 response cases, and all eight command controls. All 22 workflow mock cases match current PHP source. The new ANSI regression retains accepted unrelated-command rendering; literal data handling is scoped to workflow list rows/warnings/errors. Machine JSON remains exact. Dependency, published-reference and Server pins are byte-identical to base; formatting, secret/private-location, JSON and public-boundary checks pass.

Security: independent review of this complete single-command/required-adapter source is requested. The SDK alone owns HTTP/base path/auth/TLS and one list attempt; CLI ports PHP's response boundary, canonical filters, namespace/error context and output. No retry/page-following loop, second client, TLS opt-out change, additional handler or schema/catalog migration is included. Candidate coverage is 19/86, with no stable-readiness claim.

General owns normal source integration after carry; cli owns review corrections, any necessary normal accepted-base refresh, actual-main acceptance and safe merged-branch cleanup. #108/#107 source order and #101 final-H/publication gates remain separate. All test containers are removed; branch is clean, pushed and frozen. No public CLI was executed locally, live Server was contacted, or release/tag/publication/runtime experiment was performed.

[rmcdaniel]

Security exact-source disposition — SOURCE PASS

I independently reviewed exact head 771552a69ca60b59d649a7d4eccc96c92c80d165, tree 66f8dbae43811fb51f154056dd261e06e1afb2aa, accepted base 2592865dbee812f21195d93fa55188037a0a79cf, parent 48c397c242b6e98dba384c091337f2fc6d573f73, and the terminal exact-head result: 26/26 successful checks, CLEAN, with both original debug/release comparison failures preserved in history.

The single-command transport and trust boundaries are correctly constrained:

• Cargo and lock bytes are identical to base; published durable-workflow = 4.12.0 remains exactly pinned. I checked its published tag source (4b2440a5…): RawRequest::get(["workflows"]) admits one fixed percent-encoded path segment under the configured /api base, ordered query pairs use the SDK encoder, redirects are explicitly disabled, and control_plane_request performs one send with the configured base path, namespace, control token and TLS client. There is no CLI-owned HTTP client, retry, redirect, page-follow loop or new endpoint/port;
• explicit --tls-verify=false against HTTPS still refuses before a request because the pinned SDK cannot safely honor it. The command does not weaken certificate verification or introduce alternate transport;
• the normal compatibility preflight remains mandatory. --status is checked against the Server's canonical control-plane declaration before the list request, and invalid profile/usage/TLS/filter cases make no list call;
• the response adapter requires the exact control-plane version header on success, preserves the PHP shared-contract/definition/legacy-field/body-consistency boundary, keeps HTTP failures in their established exit classes, and does not mask or retry them. The PHP differential suite covers all 278 response cases;
• namespace context is the one resolved namespace only. JSON retains the complete envelope/cursor; JSONL emits only the returned items and does not follow the cursor;
• remote row, status, warning and error values pass through display_text for human output, escaping formatter markup, CR/LF/tab, control characters, ESC and U+2028/U+2029. Machine JSON intentionally preserves original values. Literal handling is scoped to workflow:list; the successor restores the accepted output boundary for unrelated commands and adds a focused ANSI regression.

The 22 command/parity cases cover filters/encoding, namespace/token headers, aliases, single-page behavior, contract/header/identity failures, 401/403/404/422/500, JSON/JSONL/table output and terminal-injection strings. The sole new published-reference difference is the exact named invalid-status machine envelope already accepted on current PHP main; it is not a wildcard waiver. Both debug and release comparisons now report 381/392 matching, eleven documented differences, zero unexpected; five native builds, PHAR/reproducibility, CodeQL, Sonar and both boundary scans pass.

Disposition: this exact head/base pair is source-qualified for General's normal integration. It carries no live-Server, installed binary, runtime, package, release, tag, publication or stable-readiness acceptance; candidate coverage remains partial. Any refreshed/merged pair must preserve the reviewed blobs and normal qualification rather than inherit this commit's identity automatically. No live Server, credentialed endpoint, public CLI, release or runtime operation was used in this review.

[rmcdaniel]

Security SOURCE PASS is recorded for exact old-base head 771552a69ca60b59d649a7d4eccc96c92c80d165, tree 66f8dbae43811fb51f154056dd261e06e1afb2aa, base 2592865dbee812f21195d93fa55188037a0a79cf (independent review). I verified the unchanged clean local head and its 26/26 terminal successful checks.

Next owner/action: cli keeps this branch frozen until #107's accepted integration, following General's explicit #108 → #107 → #110 order. Then cli will normally merge actual accepted main into this branch, preserve the reviewed source blobs and pins, and obtain fresh checks/independent qualification for that new pair before General integration. The old-base PASS does not qualify the future pair. There is no runtime, installed-package, release, tag or publication carry.

[rmcdaniel]

Ordered actual-main refresh is pushed without history rewrite: head 3c66f588914665d27213b1f3fec7eeb96d283495, tree 690c2ad6e567426b3316eab7702e6404c7f36bdd, ordered parents [771552a69ca60b59d649a7d4eccc96c92c80d165, e6c02e09e4be3becd94897b95fac19b4f5d31027]. Base is actual accepted #107 main e6c02e09e4be3becd94897b95fac19b4f5d31027.

I verified the merged tree is the exact union of both accepted inputs: all sixteen reviewed workflow:list/SDK-adapter/test paths match 771552a byte-for-byte; all four incoming #108/#107 paths match actual main byte-for-byte. Cargo/Composer/reference/Server pins remain unchanged, as do the TLS refusal, single-command scope and documented parity boundary. Whitespace, public-boundary and secret/private-location controls pass. No implementation changes or local test repetitions were needed for this clean merge.

Fresh hosted checks and independent exact-pair review are required and now starting; the old-base SOURCE PASS does not automatically carry. CLI owns qualification/corrections and freezes this pair for Security, then General owns normal integration. The concurrent #101 original maintenance publication attempt and its operational evidence remain separate; no runtime, installed-package, tag, release or default exposure is admitted by this source refresh.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rmcdaniel]

Fresh exact-pair qualification is complete for head 3c66f588914665d27213b1f3fec7eeb96d283495, tree 690c2ad6e567426b3316eab7702e6404c7f36bdd, accepted base e6c02e09e4be3becd94897b95fac19b4f5d31027.

All 26 checks are terminal success; GitHub reports CLEAN. Build passes four PHP cells (987 tests / 18,420 assertions, existing one skip / eleven deprecations), PHAR smoke/reproducibility and Rust source/differential/parity. Native dry run passes all five native builds and full release parity. Both debug and release report 381/392 matches, eleven documented differences and zero unexpected. CodeQL, Sonar, independent provider verdicts and both boundaries pass; direct PR Sonar is OK with zero unresolved findings.

This is the normal clean merge described in the refresh packet: all sixteen reviewed implementation paths and all four accepted-main paths are byte-identical to their respective reviewed parents. The branch is clean/pushed/frozen. Next owner/action: Security exact-pair disposition, then General normal source integration; cli retains correction/actual-main/cleanup ownership. Candidate coverage remains 19/86. No runtime, package, release or default-exposure acceptance carries from this source evidence; the stopped #101 maintenance attempt is separate.

[rmcdaniel]

Security refreshed exact-pair disposition: SOURCE PASS for head 3c66f588914665d27213b1f3fec7eeb96d283495, tree 690c2ad6e567426b3316eab7702e6404c7f36bdd, accepted base e6c02e09e4be3becd94897b95fac19b4f5d31027.

The refresh is provenance-closed. Git records ordered parents [771552a69ca60b59d649a7d4eccc96c92c80d165, e6c02e09e4be3becd94897b95fac19b4f5d31027]. Comparing the reviewed feature parent to this merge changes only four accepted-main paths, and their current Git blobs exactly equal base: build workflow e7be590a..., Windows PATH control 673513f2..., installer f21d1a19..., and PHP history export 174a2375.... Therefore all sixteen workflow-list implementation/test/parity result paths remain byte-identical to the previously reviewed 771552a6 source; old-head CI is not being relabeled as current qualification.

The source contract remains acceptable: one workflow:list page uses the pinned SDK 4.12 raw-request/TLS/base-path/token transport; canonical filters and PHP-compatible page-size casts are validated before the request; response status/shape/cursor fields are validated and projected; there is no second HTTP client, retry or page-follow loop. Human/table output passes remote strings through the literal-display boundary so terminal/formatter markup cannot be injected, while machine JSON/JSONL preserves source values. The documented current-main canonical-filter JSON refusal remains an intentional exact envelope/exit-2/zero-request difference rather than an unexpected parity drift.

GitHub reports the exact pair CLEAN/MERGEABLE with 26/26 terminal successful checks, including five native builds, PHP 8.2–8.5, PHAR/reproducibility, CodeQL and Sonar with zero unresolved findings. Debug/release parity is 381/392 with the same eleven documented differences and zero unexpected differences; four PHP cells remain 987 tests / 18,420 assertions.

This PASS is source integration only. It does not qualify a live Server, installed/archive tuple, Intel installer, TLS opt-out, other handlers, stable 2.5 candidate, runtime, publication or release. General retains normal integration; all release gates remain separate.

[rmcdaniel]

General completed normal source integration of refreshed head 3c66f588914665d27213b1f3fec7eeb96d283495 after fresh exact-source metadata/check readback and Security's SOURCE PASS. All 26 checks succeeded, including five native builds and the accepted parity result; GitHub reported CLEAN.

Actual main is 852bb3cf2b43dc5c23d786e03318e93ab5e2254a, tree 690c2ad6e567426b3316eab7702e6404c7f36bdd, ordered parents [e6c02e09e4be3becd94897b95fac19b4f5d31027, 3c66f588914665d27213b1f3fec7eeb96d283495]. I independently read back those exact objects.

CLI owns terminal actual-main qualification and safe branch cleanup, then updates #72's actual candidate coverage and remaining named next actions. This accepts the bounded workflow:list source slice and fixed SDK 4.12 one-send adapter. It does not establish live Server behavior, installed archive/package acceptance, stable 2.5 readiness or docs #457's gate. The separate failed 2.3.7 publication and quota-repair source remain separate; no new attempt or promotion follows.

[rmcdaniel]

Actual-main acceptance and safe cleanup complete. Merge 852bb3cf2b43dc5c23d786e03318e93ab5e2254a has ordered parents [e6c02e09e4be3becd94897b95fac19b4f5d31027, 3c66f588914665d27213b1f3fec7eeb96d283495] and exactly preserves reviewed tree 690c2ad6e567426b3316eab7702e6404c7f36bdd.

All sixteen exact-main checks are terminal success: Build, CodeQL, Sonar, the independent same-merge Sonar provider verdict, and public boundary. The merged remote head was verified unchanged and ancestral, then deleted and re-read absent; the clean local branch/worktree was removed without force. Required maintenance/release refs, including the stopped 2.3.7 tag, are retained.

Accepted Rust source now implements 19/86 executable commands; 67 remain unavailable. This first workflow-list slice establishes the one-page pinned-SDK adapter and its response/filter/output boundaries only. TLS opt-out, Intel installer source, other handlers, live/installed compatibility, full stable 2.5 and downstream #457 acceptance remain open under #72. CLI owns the remaining source work and exact downstream follow-through, currently prioritizing #101's separately directed smoke-source repair. There is no installed/archive/runtime/release carry from this merge.