platelisted

# /plate Plate completes local work before review. It finishes required artifacts, validates, commits safely, and selects the correct publication path. ## Phase entry Run `python3 skills/plate/scripts/plate.pyz wheypoint-resolve --ref <slug>`. `authoritative` uses the record; its `working_context` is the first batched `tilth_read`. `not-found` proceeds cold; `legacy` shows its source and slug, then proceeds. `gated`, `ambiguous`, and `error` stop and show the payload. Show advisory `stale-commit` and `grounded-path-missing` findings. Plate resolves the slug and reads the result, but it does not commit a wheypoint revision or publish a wheypoint revision. ## Routing guard Check ownership before you select a mode. `/plate` owns staging, commits, pushes, ordinary pull request changes, and pull request stack changes. - `/plate` never performs code-quality review. It never computes a review surface for its own sake. Review is `/age`. - `/gh` owns GitHub inspection, reviews, comments, CI, merges, issues, workflows, releases, search, and administration. Use `/gh` when no local publication transaction is necessary. - A request that only reads or assesses GitHub or diff state leaves `/plate` before any mode is selected. Thus, routing it here is a plate-owned failure. - Destructive deletion, history rewrites, unsafe force-pushes, and protected-branch changes require explicit user authorization. ## Classify, then load one reference Classify every invocation into exactly one