Fix P112 workflow parse failure caused by runner context in job env

[Clear1nsight]

Change and mathematical scope

Fix the pre-job parsing failure in .github/workflows/p112-common-slice.yml. The original job-level env uses runner.temp, although the runner context is unavailable in jobs.<job_id>.env. Replace it with an initial run step that writes TMPDIR=$RUNNER_TEMP/p112-common-slice to GITHUB_ENV for subsequent steps.

This is one workflow file and one commit. The upstream repository guard, manual workflow_dispatch trigger, resource bounds, scientific commands and source inputs retain their behaviour. No scientific, selected-result or research-package change is proposed.

Task and overlap

Tooling/CI repair, unchanged scope from fork PR Clear1nsight#8. Exact head: 89031d2. The comparison against canonical main 20ecf28 confirms that the only changed file is the P112 workflow; the fork's older-main lag does not introduce unrelated changes. Current AGENTS.md, autoresearch.md and CONTRIBUTING.md were read. This repair is kept separate from the QQ16 and staged544 research PRs whose pushes exposed the same shared parse failure.

Validation

The original diagnosis records instantaneous failed runs with zero jobs and the filename as run name, including https://github.com/Clear1nsight/integer-mult-bounds/actions/runs/39189206135 and https://github.com/Clear1nsight/integer-mult-bounds/actions/runs/39189759307. Context reference: https://docs.github.com/en/actions/reference/workflows-and-actions/contexts.

The repaired branch push did not create a new failed P112 validation run, consistent with removal of the pre-job expression error. That observation is not a successful manual upstream P112 scientific replay. The focused diff was inspected in the browser for this submission; no new execution, broad historical suite or source regeneration was performed. Maintainer verification should confirm workflow parsing and, if desired, run the upstream-only manual workflow after incorporation.

Credit

Repair by Clear1nsight with OpenAI assistance. Existing workflow authors, research attribution, Apache-2.0 and source notices are retained.

Open next questions

No new mathematical investigation is justified by this workflow-only repair. Remaining operational check: confirm parser acceptance and manual upstream P112 execution; upstream-only execution cannot be inferred from fork behaviour.

Workflow feedback

The original connected integration could create the fork review but returned HTTP 403 for upstream creation. This browser submission publishes the same isolated fix upstream.

Consolidation checkpoint (2026-10-19 UTC)

This remains the canonical focused P112 repair at 89031d21f01f8b676f87c76443f5afc41457a17c. Against refreshed canonical bb4bccbf42844d2801487450727c2f63e10d1d0f, the workflow change still consists solely of moving TMPDIR initialization from the invalid job-level runner context into the first run step. actionlint 1.7.12 rejects the original at the job env expression and accepts the exact repaired file (optional shellcheck/pyflakes disabled). The repository restriction, workflow_dispatch trigger, resource bounds, checkout pin, scientific commands and source inputs are preserved. This parser validation is not an upstream manual scientific replay.

Identical P112 repair bytes also occur in research PRs #3554, #3577, #3609, #3620, #3623, #3828, #3873, #3882, #3883, #3884, #3886, #3931, #3936 and #3941. Those repairs remain in place until this focused fix is incorporated into the upstream base. Do not revert them first and reintroduce a known invalid workflow. Once incorporated, compare each exact head against refreshed main and use additive merges only where needed; do not rewrite scientific source pins or frozen publication evidence.

The other shared changes in #3577 have separate byte-preserving extraction commits based on current canonical main: ledger/reconciliation 1f360c63d00289aa5be2300d8c72e7bcf86827fe (11 files) and historical receipt adapters 161ce1b96288349fd67ecda1734d2f96850a2ee9 (9 files). They require their own substantive review, not inclusion in this one-file workflow PR. The separate upstream draft proposals are #4102 (ledger/reconciliation) and #4103 (historical receipt adapters), published through the authenticated browser after the connected integration returned HTTP 403. No maintainer merge or research-branch rewrite has been performed.