fix(ops): shadow trajectory daily-tick automation via systemd (FIX-5)

[neuron7xLab]

Creator

New scripts/shadow_daily_tick.sh wrapper runs the full daily ritual (tick → pipeline_status → eval → verdict → DP3 → trajectory.log) and is bound as ExecStart of the existing ops/systemd/cross_asset_kuramoto_shadow.service. Closes the manual-cadence failure mode for the 75-bar window before the 2026-07-10 truth gate.

Critic

• Edge-case 1 — paper_trader.py --tick may fail (rate limit, network blip). Wrapper catches non-zero rc, logs FAIL, continues. The eval/verdict downstream still runs against the prior paper-state.
• Edge-case 2 — make eval-tick is idempotent on results/shadow_live.json but appends to LIVE_SCOREBOARD csv. Acceptable: the eval was already idempotent against duplicate dates.
• Edge-case 3 — DP3 test raises ValueError at bar < 3. Wrapper handles via 2>/dev/null || true and substitutes UNAVAILABLE in the trajectory line.
• Risk — systemd 255 changed journalctl --user -u SERVICE parsing; the FIX-5 falsification gate must use --user-unit=SERVICE (combined form). Documented in the acceptor + commit body. Older systemd installs that still accept the separate-flag form remain compatible.

Auditor

Falsification gate (FIX-5): after a successful invocation, journalctl --user-unit=cross_asset_kuramoto_shadow.service --since='-1 day' MUST contain at least one tick: ok line. The literal string is emitted only as the final wrapper step, after trajectory.log append; partial / failed runs do NOT emit it.

False-positive avoidance:

• tick: ok is gated to the END of the wrapper. Earlier failures abort via set -euo pipefail and never reach the line.
• The acceptor's falsifier block probes systemctl --user is-active cross_asset_kuramoto_shadow.timer; if disabled/masked, FIX-5 is broken regardless of journal content.

Verifier

```
$ systemctl --user is-active cross_asset_kuramoto_shadow.timer
active

$ systemctl --user start cross_asset_kuramoto_shadow.service
$ sleep 5

$ journalctl --user-unit=cross_asset_kuramoto_shadow.service \
--since='-1 day' --no-pager | grep -c 'tick: ok'
2

$ tail -1 results/sharpe_trajectory.log
2026-05-06T13:38:46Z bar=15 sharpe=-3.92 ci=[-13.76,+0.43] verdict=AMBIGUOUS dp3=REJECT
```

The single dated trajectory row at the end is the canonical signal of a successful FIX-5 invocation: it composes FIX-1 (pipeline_status→op_unsafe), FIX-2 (shadow_live.json), FIX-4 (CI-aware verdict), and FIX-3 (DP3 honest test) into one observable line.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c92575d433

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Fail the wrapper when paper_trader --tick exits non-zero

The --tick command failure is explicitly swallowed here, so the unit keeps running and can still emit the terminal success marker (tick: ok) even when no new bar was advanced. In environments with transient API/network errors, this creates false-positive health signals for FIX-5 and allows trajectory/eval outputs to be produced from stale paper state instead of the intended daily tick.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Treat missing paper_trader path as fatal

If the configured SPIKE_TRADER file is absent, the script logs SKIP and continues instead of failing, which means the systemd run can appear successful without performing the core daily tick. On any host where the spike checkout path differs or is missing, this silently defeats the automation objective while still letting downstream steps and monitoring proceed as if the tick happened.

Useful? React with 👍 / 👎.