[actools-pl]

CP-001 — E01-H hosted-CI evidence

This draft PR publishes the exact independently reviewed CP-001 candidate solely to obtain the required GitHub-hosted Source CI evidence. It is not merge authorization or task acceptance.

Exact identity

Field	Value
Repository	actools-pl/actDrupal
Base branch / exact expected base	main / dce4e44b13ab19c65d8e9b67243bfeb72a15cdb2
Head branch	task/CP-001
Exact candidate	2aafec4c15a8ea1f05a2a4d97268b8dd1e3fbbec
Candidate tree	4ca87f34300ba92e37f3e331d8e5ce1805fb41d0
Cumulative affected-file boundary	27 paths
Route	Human Git normal non-force publication; draft PR for hosted-CI evidence

Review/evidence status before publication

• F01–F06 source corrections: independently verified.
• Ubuntu target corrected to the authoritative Ubuntu Server 26.04 LTS line.
• Resolver-generated CI lock: reviewed and bound to this candidate.
• Local E01: independently accepted for this exact candidate after Ubuntu 26.04.1 / x86_64 / CPython 3.14.7 hash-locked install, real wheel/launcher/import checks, real pip-audit, canonical SOURCE-CI: PASS, exact generator-provenance receipt and source-integrity readback.
• Remaining technical gate: E01-H, the real GitHub-hosted ubuntu-26.04 Source CI execution.

Hosted-CI purpose

The source workflow is expected to run on the GitHub-hosted ubuntu-26.04 x64 runner using CPython 3.14.7 and the pinned/hash-locked CI dependency closure. The E01-H receipt must bind the actual workflow/run/job and tested head or GitHub-generated merge subject back to the exact candidate above, and retain runner/image, tool versions, step conclusions and logs.

Current authority boundary

The owner authorized only:

• publication of the exact task/CP-001 candidate above;
• opening this one draft PR to main;
• read-only observation and evidence collection for the resulting hosted Source CI run.

The authorization does not permit source changes, a new source commit, force-push, workflow rerun, alternate runner, repository/Actions settings changes, branch-protection/ruleset changes, required-check configuration, ready-for-review transition, merge, auto-merge, branch deletion, release publication, deployment, or server operations.

If hosted CI fails, is cancelled, cannot schedule, tests an unexpected source, or yields ambiguous evidence, stop and report the exact result. Successful CI is evidence only; human CP-001 acceptance and integration remain separate decisions.

No merge authorization.