[rmcdaniel]

Part of #325: API parity. Native now serves POST /api/workflows/{id}/terminate and POST /api/workflows/{id}/runs/{run}/terminate.

Published Workflow runs cancel and terminate through one implementation (attemptTerminalCommand), so native does the same. Terminate records:

• its own command type, TerminateRequested and WorkflowTerminated;
• the terminated status, closed reason, failure category and propagation kind;
• WorkflowTerminatedException.

It closes open tasks, activities and timers exactly as cancel does. A late activity outcome is refused with run_terminated. The response carries the terminate control-plane contract, which matches cancel's.

Terminating a child run is refused with 422 termination_propagation_not_available, and nothing changes. The parent-side ChildRunTerminated projections need their own fixture first; the port log lists this gap.

Fixtures

• The immediate cancellation fixtures take a command; it defaults to cancel.
• terminate-before-claim, terminate-pending-timer and terminate-leased-activity reuse the cancellation workflows.
• The shared contract and its runner unit tests check the termination identity in place of cancellation's.

Checks

• A local copy of the SQLite parity step recorded published PHP 2.5.14, embedded PHP and native. All six cancel and terminate fixtures passed on every target, and the comparison passed.
• Native integration tests for both commands pass on SQLite, PostgreSQL and MySQL. The SQLite library and execution suites pass.

The worker listing PR stacks on this branch, so its parity run qualifies both. This branch's own parity run is cancelled as a duplicate.

🤖 Generated with Claude Code

[rmcdaniel]

Cancelled this branch's parity run 39454777693: #544 stacks on this branch, and its parity run 39454805674 qualifies both.

[rmcdaniel]

Merged main (49a56f5c0, which adds #551 namespace update, #545 database TLS and #556 certifi) into this branch as e7b8dfbed. The only conflict was in the port-log checkpoint list, and I kept both entries.

Parity. I cancelled the Shared Server fixtures run for the merged head (39506903121) as a duplicate:

• the branch's own change is unchanged since 39484509609, which passed all 13 jobs on 2d6b1e99d;
• main's additions run their own parity after each merge;
• runners are congested.

Local check of the merged head. On SQLite, the native lib suite (122) and the execution suite (291) pass.

Auto-merge is on for the required checks.

[rmcdaniel]

09d249ca7 merges main again (f4937bed6, #549 multi-node harness). That change touches no native code, parity script or parity workflow, so I cancelled the duplicate Shared Server fixtures run 39508690780. The qualification remains 39484509609.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud

[rmcdaniel]

The opt-in native packaging proposal in comments 6301678221 and 6301964569 is accepted for source preparation: build the locked native executable for both architectures inside the existing image, retain PHP as the published default, and require both the explicit engine selection and existing native experimental guard. Preserve current immutable-image identity checks and PHP startup/management behavior. Unknown engine values must refuse clearly; native selection must not run PHP migration or config-cache commands against native storage.

Qualify the actual two architecture images, engine/command selection, database ownership refusals and shutdown before any native packaging claim. This approval is not native runtime or migration acceptance.

For the immediate main promotion order, please acknowledge #552 as the next merge/tag handoff. Its preceding combined head passed the full PHP suite, but main changed again through #543 before protected merge; this is the third ancestry cycle for unchanged PHP. The maintainer is integrating adefcf8 and running fresh normal gates. Finish that qualified merge and immutable PHP 2.9.11 tag before the next native main promotion. Independent native branches, review and admitted qualification continue during this short release handoff. Please acknowledge this order on #552 or #325 so both maintainers have the same decision.