# Media Workbench Worker Contracts

> Guard the STARFRAME Media Workbench worker ownership contract, queue/work-item lifecycle, and desktop-to-worker status surfaces. Use when changes touch `9040`, job payloads, resumable work items, operator snapshots, or worker-facing docs/tests.

- Skill: `grtninja/media-workbench-worker-contracts` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add grtninja/media-workbench-worker-contracts`
- Raw SKILL.md: https://api.skillmd.com/api/skills/grtninja/media-workbench-worker-contracts/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: grtninja (https://skillmd.com/u/grtninja)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/grtninja/media-workbench-worker-contracts

---


# Media Workbench Worker Contracts

Use this skill when the Media Workbench `9040` worker contract changes and the desktop shell, queue lifecycle, and operator-visible state all need to stay aligned.

## Workflow

1. Read the target repo `AGENTS.md` and the operator app contract first.
2. Treat the repo as the sole owner of the `9040` worker contract, local dashboard, and thin desktop shell.
3. Inspect these worker surfaces together:
   - `/health`
   - `/ready`
   - `/v1/media-agent/status`
   - `/v1/media-agent/jobs`
   - `/v1/media-agent/summary`
4. Preserve operator-visible workflow state:
   - `active_job_id`
   - queue depth and tracked jobs
   - resumable work item target
   - draft state continuity
   - output/artifact visibility
5. Validate desktop-to-worker coupling:
   - healthy worker reuse when already up
   - repo-owned bootstrap when down
   - queue, cancel, retry, and resume-latest routes stay consistent
   - runtime snapshot and operator snapshot still describe the same active systems
6. When job payloads or status fields change, update Electron IPC, docs, and tests in the same pass.

## Required Evidence

- worker health and ready proof
- current status or summary payload
- queue or work-item lifecycle proof for the changed path
- note of any operator-visible field that changed
- exact docs/tests updated with the contract change

## Guardrails

- Sister repos may submit work through the worker, but they do not redefine the contract.
- Do not hide or silently reset active job, draft, or resume state.
- Keep source-by-reference behavior intact; do not duplicate the source library to satisfy the UI.
- If worker health, queue lifecycle, or resume semantics are ambiguous, fail closed and report the contract as unresolved.

## Best-Fit Companion Skills

- `$media-workbench-desktop-ops`
- `$local-compute-usage`
- `$docs-alignment-lock`
- `$skill-common-sense-engineering`

## Scope Boundary

Use this skill only for the Media Workbench worker contract and its desktop/operator coupling.

Do not use it for:

1. generic Comfy workflow tuning without contract changes
2. full training-workbench tasks
3. VRM or avatar runtime work

## References

- `references/worker-contract-checklist.md`

## Loopback

If this lane is unresolved, blocked, or ambiguous:

1. capture the failing worker route or status field
2. route back through `$skill-hub` for chain recalculation
3. resume only after the updated chain returns a deterministic contract fix path