heliographlisted

# heliograph Someone can reach the machine. You cannot, and you are the one who knows what to ask it. This skill runs that gap as a loop instead of a relay: **git carries the step out and the log back**, and the operator types one command that never changes. ``` you push a step ────────���─────────────────────▶ transport repo operator ──────▶ git pull && ./run.sh the log is captured and pushed ──────▶ transport repo you git pull, read ops-logs/<step>-<UTC>.txt ◀── ``` Every captured line carries a UTC timestamp, ANSI is stripped, obvious secrets are masked, and the log is committed and pushed **whether the run passed or failed**. ## When this applies - The machine is in an environment you have no interactive access to. - The only person who can reach it has other work to do and should not be your terminal. - Several rounds of "run this and paste the output" have already gone badly. - The repo that has to *change* is also on the far side (see [references/remote-repo.md](references/remote-repo.md)). If you can SSH in yourself, do that instead and do not use this skill. ## Where this sits This skill is the **far side and the method**: the payload that runs on the machine, and how to debug across a gap. It needs nothing installed there, and that constraint is the whole proposition. The **near side** - your machine - has two optional things that make the same loop easier to drive. Neither is required, and n