Skip to content

CruxExperts/LocalSetup / ls/skills/ls-codex-heartbeat-checks

ls-codex-heartbeat-checks

Verified

Opt-in agent heartbeat harness for target repositories: initialize config, run transaction-safe checks, preserve artifacts, and wire cron only after explicit activation.

references/transactions.md

View on GitHub
---
status: ACTIVE
version: 3.4
---

# Transactions

The ordinary heartbeat run uses this file transaction:

1. Acquire `heartbeat.lock`, or return current owner evidence without touching state.
2. Recover abandoned staged runs only while holding the lock.
3. Create `runs/<run-id>.staged`.
4. Write `active.json`.
5. Run hooks and the optional configured agent command.
6. Write the result, command log, sidecars, and manifest hashes.
7. Validate the staged artifact graph.
8. Atomically promote to `runs/<run-id>`, update `latest.json`, and remove `active.json`.

If validation fails, the staged run is not promoted as successful. Future ordinary
lock-owning runs preserve abandoned staged work as recovered failure evidence.

[Reserved actions](config.md#running-a-reserved-action) use the same overlap lock
with separate protected reservation/result accounting. They do not run hooks or
perform the staged transaction above; reserved `--no-agent` skips before lock
acquisition. Follow [reserved execution](process-control.md#reserved-execution-owner)
and [result reconciliation](recovery.md#reserved-result-acknowledgement-recovery)
for that route. Ordinary recovery preserves failure evidence but does not block
subsequent configured runs pending effect reconciliation. Operators must reconcile
uncertain effects before repeating a command; reserved execution enforces its
separate reconciliation gate.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall