- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add amplifthq/openmeld --skill verify-runtime-coordinator-liveness -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add amplifthq/openmeld --skill verify-runtime-coordinator-liveness -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add amplifthq/openmeld --skill verify-runtime-coordinator-liveness -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add amplifthq/openmeld --skill verify-runtime-coordinator-liveness -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/amplifthq/openmeld/tree/HEAD/.agents/skills/verify-runtime-coordinator-liveness게시자 제공
A running Wake is not failed for silence while accepted progress is inside the window: five minutes normally, thirty minutes when the communication-recovery baseline is still that same progress. An unanswered question pauses that decision. The first of reply, stop, or failure sticks. Harm: a long task dies while the agent is still reporting, or a reply and a failure both become the Space outcome.
The question is the order of progress, time, disconnect, stop, and reply. That is a model check, so the spec is TLA+ and the checker is TLC 1.7.4 (jar sha256 936a262061c914694dfd669a543be24573c45d5aa0ff20a8b96b23d01e050e88). The code check calls the stale-progress predicate and both terminal settlement functions. Java 11 or newer must be on PATH. The check downloads the jar into ~/.cache/openmeld-tlc/ on first run.
Run it when a change touches any of these:
services/core/src/runtime-transport/application/runtime-coordinator-authority.ts
hasRuntimeCoordinatorLocalProgressStaleTerminalExpiredRUNTIME_COORDINATOR_PROGRESS_EVIDENCE_STALE_TERMINAL_AFTER_MSRUNTIME_COORDINATOR_COMMUNICATION_RECOVERY_WINDOW_MSsettleRuntimeCoordinatorAuthorityForTerminalDecisionsettleRuntimeCoordinatorAuthorityForCancellationAcceptedservices/core/src/runtime-transport/infrastructure/postgresql/runtime-coordinator-execution-repo.ts
LOCKED_TERMINAL_STATUSESConfirmed against commit 965d9eb3219fa2c35789f9ab9a2206ab8699de9b. Move that commit forward only after you have confirmed that RuntimeCoordinatorLiveness.tla and check.test.ts still describe those functions.
From the repository root, after pnpm install:
node .agents/skills/verify-runtime-coordinator-liveness/check.mjs
Exit 0 means fresh progress is not a failure and a later stop or timeout preserves the recorded terminal outcome.
Read every TLC result with /statechart. The user-facing labels are in view.mjs next to the spec.
does not fail a wake while it is waiting for the user failed: an open question no longer pauses the watchdog.FreshProgressIsNotAFailure or TerminalOutcomeSticks failed in TLC: either the model gained a step the code does not have, or you need to add a step the code does have. Time in the spec is a 5-minute tick, from 0 through 6. Do not raise the tick limit to hide a counterexample.TerminalOutcomeSticks compares consecutive states. A model that allows a published reply to become a stop fails even if both fields change together. The code check independently applies a late stop to a published reply and a late timeout to a settled stop. The PostgreSQL ledger is outside this executable replay.
One accepted Wake. Left out: pre-accept redelivery, token mismatch, and failed_retryable. The chart hides stop, reply, and "the agent asks you" from the states where the computer is already away. Those actions still exist. Stop and reply are shown from Working, and stop is also shown from "No progress for five minutes".
Use /maintain-formal-verification-skill to bring this check back in line.
Check RuntimeCoordinator liveness for one workstation Wake. Fresh progress is not a failure, an open question pauses the stale watchdog, and the first terminal outcome sticks. Use when changing hasRun
---name: verify-runtime-coordinator-livenessdescription: Check RuntimeCoordinator liveness for one workstation Wake. Fresh progress is not a failure, an open question…---# .agents/skills/verify-runtime-coordinator-liveness/SKILL.md개요
Check RuntimeCoordinator liveness for one workstation Wake. Fresh progress is not a failure, an open question pauses the stale watchdog, and the first terminal outcome sticks. Use when changing hasRuntimeCoordinatorLocalProgressStaleTerminalExpired or the terminal settle functions.
FAQ
게시자에게서 .agents/skills/verify-runtime-coordinator-liveness/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/amplifthq/openmeld에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.