Repository navigation
Isolate the Process engine’s Ticket source and publication - #1907
Merged
Merged
Conversation
This was referenced Nov 9, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Put the Process engine's Ticket source and publication policy behind a factory/local seam. Factory execution keeps its existing behavior; the local adapter runs the Built-in Ticket run through Security review and stops before Delivery.
Closes #1873
Evidence
Execution evidence
thirdshift --trial <request.json>on a local fixture repository and issue file; observe committed implementation, Security review, restored issue hand-over, Step/session artifacts and absence of GitHub publication.deliveryandself-mergelocally.cargo test --test trial process::built_in_ticket_steps_run_locally_without_publication -- --exactagainstissue-1484, with the new regression:FAILED,invalid Trial request: unknown variant process, expected code-review or spec-review.After: the same command passes:
1 passed; 0 failed. It runs both Steps, restores the supplied issue file, commits locally, makes noghcalls or pull request, and stops before Delivery.cargo test --bin thirdshift processes::source::tests::local_source_refuses_publishing_steps -- --exact:1 passed; 0 failed; both publishing Steps are refused with clear errors.cargo clippy --all-targets -- -D warnings: passed.cargo fmt --all -- --checkandgit diff --check: passed.UPDATE_PROMPTS=1 cargo test --bin thirdshift prompts_page:14 passed; 0 failed; generated files are unchanged.CARGO_BUILD_JOBS=2 RUST_TEST_THREADS=3 /usr/bin/time -p scripts/affected-tests issue-1484: stopped at one existing Console I/O assertion after 1,662 unit tests and the preceding integration suites passed. The Console suite had263 passed; 1 failed; 1 ignored.cargo test --test console idle::unchanged_requests_reuse_retained_records_but_replacements_are_visible -- --exact --nocapture: fails on this branch and on untouchedissue-1484, both withunchanged request reread 107679 bytes(limit: 48 KiB). No Console source or test is changed here.cargo test --no-fail-fast, selected from Cargo metadata after the stoppedconsoletarget (RUST_TEST_THREADS=6, Python 3.11). Wall time: 1595.32s, warm build cache, no compilation. This includes the unchanged Process, Ticket-run, Security-review and Spec-run tests and the new local Trial test.Validation selects Python 3.11 through a temporary PATH shim. This host's default Python 3.9 lacks
tomllib, required by the existing Bug-origin regression. The exact previously failing selector,cargo test --test bug_origins settlement::historical_review_and_reclosed_origin_regressions -- --exact, passes with Python 3.11.Unaddressed findings
Standards
None. The one Standards finding (duplicated Trial result construction) was addressed by sharing result finishing across execution paths; the reviewer confirmed the fix.
Spec
None. The Spec review raised no findings.
Security
None.
Security review outcome
No unaddressed introduced findings.
Review coverage
Both independent reviewers read all 12 changed files. No changed file was left unread, and no generated output was excluded. Reports and final files-read lists are retained in
.thirdshift-review-71CgQm/standards.mdandspec.md;summary.jsonrecords{"standards":1,"spec":0}before implementation decisions.Merge Danger
Door: two-way
Blast Radius: Process
The factory adapter moves existing acquisition, issue checks, implementation, Security review and Delivery code. The local adapter has no publishing implementation.
Built with codex codex-cli 0.166.0 · gpt-6.1-sol · xhigh