Prompt-pack worker (system)

Feature FW-WC-009. Status: published.

Updated

Intent

Laptop-only workcell: register a prompt zip, require approve, run write-capable Cursor as Grok 4.7, scan completion evidence, post AUDIT, and run deploy only after a separate deploy reply.

Behavior

Item Value
Runtime forge-agents cursor_bridge, matrix-adapter on the operator laptop
Room #cursor-plain
Model grok-4.7-high; fails closed if that id is absent from cursor-agent models
Data ~/.local/share/forge-prompt-pack/<pack_id>/
Ledger prompt-packs.db beside the bridge store
Zip ≤20 MB, ≤200 files, .md / .txt only, no traversal or symlinks
Turns Max 3 implement turns
Deploy Allowlisted scripts under the Code workspace or ~/forge-fleet

Completion scan reads promotion_decision.json, acceptance_status.json, CHECKPOINT.json, and the deploy plan. The in-thread dual-wiki reply checks that summary.md names the same decision as promotion_decision.json and that every zip acceptance id has a status row. That reply is a pack check, not this handbook pair.

Progress for long steps is one edited Element message (m.replace). AUDIT, IMPLEMENTED, and TEST stay separate events.

Limits

Not the Granite agentic_dev rail. General !agent new stays approval-gated; only this workcell may spawn write-capable Cursor on the laptop. Deploy rejects ssh, &&, force-push, and --no-verify. commit does not push main. fix and catchup do not mark a skipped check as pass.