Affected Repositories

• PyAutoHeart (primary, and the only repo changed)

Branch Survey

Suggested branch: feature/heart-smoke-table-autocti

Implementation Steps

1. .github/actions/install-arcticpy/install_arcticpy.sh — new. Carries the recipe verbatim (GSL, build deps, runtime deps, the pinned build, the importlib.metadata verify) plus the long WHY comment. Env contract: ARCTICPY_VERSION (default 2.6 — the pin), ARCTICPY_INSTALL_GSL, ARCTICPY_SUDO, PYTHON (default python). Writes version= to $GITHUB_OUTPUT only when that variable is set, so it is equally usable outside Actions.
2. .github/actions/install-arcticpy/action.yml — its five run-steps collapse to one bash "${{ github.action_path }}/install_arcticpy.sh" with the inputs mapped to those variables. Inputs, defaults and the version output are unchanged, so every consumer is byte-identical at the call site.
3. config/repos.yaml — PyAutoCTI: autocti in import_names; autocti and autocti_test entries carrying arcticpy: true.
4. heart/smoke.py —
   • WorkspaceSpec gains arcticpy: bool (default False); load_smoke_config reads it.
   • _install_environment runs the shared script before the workspace epilogue when the flag is set — the same order as CI.
   • environment_fingerprint hashes the shared script under a fixed key when the flag is set, so editing the recipe or bumping the pin invalidates the cached environment instead of silently reusing a stale one. (It cannot go through the existing relative_to(organism_root) path — the script lives in the Heart checkout, not the organism root.)
   • GSL probe with an actionable error naming the apt line.
5. Tests — tests/test_smoke.py / tests/test_repo_config.py for the new key, the fingerprint sensitivity, and the ordering.

Verification (the acceptance criterion)

Prepare a CTI environment through the local runner and run a suite through it. autocti_workspace_test is the cheap one (~20 s); autocti_workspace is the new 132 s suite.

Key Files

• .github/actions/install-arcticpy/{action.yml,install_arcticpy.sh}
• config/repos.yaml — the smoke: block
• heart/smoke.py — WorkspaceSpec, load_smoke_config, _install_environment, environment_fingerprint

Two traps not to rediscover

• --no-deps suppresses arcticpy's runtime imports too: arcticpy/read_noise.py imports scipy and matplotlib, and __init__.py imports it.
• arcticpy exposes no __version__. arcticpy.__version__ raises AttributeError on a healthy install; use importlib.metadata.version("arcticpy").

Heart's local smoke runner cannot run any CTI workspace — no autocti entry

Type: maintenance
Target: pyautoheart
Repos:

• @PyAutoHeart
  Difficulty: medium
  Autonomy: supervised
  Priority: normal
  Status: formalised
  Filed: 2026-08-24

PyAutoHeart/heart/smoke.py is the local smoke runner — "one isolated
environment per workspace, prepared from the workspace-owned installer", the
local mirror of what CI does. Which workspaces it can prepare is declared in
config/repos.yaml under the smoke: block, and the CTI repos are absent
from it entirely.

So pyauto-heart smoke autocti cannot work, and neither can a local smoke run of
autocti_workspace_test — the only way to exercise CTI smoke is to push and let
CI do it. That is a slow loop for the repo group that has just acquired two smoke
suites.

Work

1. Add PyAutoCTI: autocti to smoke.import_names.

2. Add the two workspace entries with the correct chain
   ([PyAutoNerves, PyAutoFit, PyAutoArray, PyAutoCTI]).

3. Handle arcticpy. This is the real design question. A composite action
   cannot be invoked from heart/smoke.py, so the local runner needs an
   equivalent. Decide deliberately between: factoring the recipe into a shell
   script that both the action and smoke.py call; a small Python leg in
   smoke.py that mirrors it; or a per-workspace arcticpy: true flag in the
   smoke: block that smoke.py honours.

   Whatever is chosen, there must remain exactly one place the recipe and the
   2.6 pin live. Re-creating a second copy would undo PyAutoHeart#170.

4. Verify by actually running it — prepare a CTI environment through the
   local runner and run both suites, not just "the config parses".

Context

PyAutoMind/complete/2026/08/arcticpy-install-standardisation.md — why the
recipe has one owner and what breaks when it does not.