granoflow-gfmcp-runner

Granoflow GFMCP Runner

Use this skill when installing, operating, or diagnosing the optional GFMCP automatic task worker. The worker polls Granoflow every five minutes, considers only pending tasks tagged GFMCP, and delegates one eligible task at a time to an authorized local agent.

Keyword

• #gfmcp-runner
• #gfmcp
• #gfmcp-worker

Safety Contract

• The tag is an eligibility signal, not blanket authorization.
• Before any phase that needs authorization, re-read the delegated owner receipt and run granoflow-delegated-authorization's validator. Continue only on decision=allowed; decision=denied routes to the existing visible waiting workflow. The worker never constructs or confirms its own envelope.
• Call POST /v1/ai-agent/gfmcp/prepare before polling. Granoflow owns the localized tag description template.
• Call POST /v1/sync/gfmcp-safe-run before reading candidates. Granoflow decides whether cloud sync is allowed; guests continue locally and uncertain authorization fails closed.
• Never print API tokens, task bodies, private failure details, or agent transcripts.
• Safe local inspection and reversible workspace edits may proceed. Publishing, payment, login, external messages, destructive changes, secrets, or broadened scope require explicit user authorization.
• Missing necessary information must be written into the task as a concise waiting/blocker note. Do not invent credentials or business choices.
• A task is complete only after Granoflow API readback reports status=done. An agent process exit code is not completion evidence.
• A task with Plan nodes must write and content/hash-readback Task Delivery before the final required node, then complete only through NodeService. A node-less compatibility task may use one finish call after its applicable Delivery gate.
• Ordinary completion does not create deep Task Review or a new Card Checkpoint. It consumes the Delivery checkpoint already recorded by the task workflow.
• An unattended worker may read linked cards and record phase candidates, but it cannot infer approval for card writes. Delegate every card search, draft, preview, confirmation, and write to granoflow-review-card-draft; record unapproved operations as deferred and never create hidden card drafts or cards.
• An unattended worker never starts a daily review, drafts mood/efficiency notes, or writes a journal. If an interactive user separately requests one, delegate to granoflow_daily_review_skill.