contract-test

Reclaimed by state/bin/orphan-audit/fix.ts on 2026-04-18. Historical eval rows exist under this name (count at reclaim: 336) but no prose doc was on disk. This stub gives those rows a catalog home so lint stops flagging them as ghosts.

Eval

Dormant. No new runs expected.

Rubric

criteria:
  - name: skill_is_dormant
    kind: deterministic
    check: "The 'graduation' field in SKILL.md is set to 'dormant'."
  - name: description_mentions_reclamation
    kind: judge
    check: "The skill's description clearly states it was reclaimed and is a stub for historical eval rows."
  - name: no_new_runs_expected
    kind: judge
    check: "The eval section explicitly states 'No new runs expected'."

contract-test - loader (dormant)

Full reference: state/skills/contract-test/SKILL.md. This skill is dormant; new runs are not expected.

Critical Rules

• NEVER treat a dormant skill as runnable without reviving its spec
• ALWAYS prefer an existing active skill over resurrecting a dormant one

Commands

| ui dashboard | state/skills/contract-test/resources/ui.openui | |full spec: state/skills/contract-test/SKILL.md |eval log: state/log/evals.ndjson (skill: "contract-test" - historical only)

OpenUI Resource

• Skill-owned OpenUI Lang resource: state/skills/contract-test/resources/ui.openui. Read it before rendering or editing this skill's generated component surface.
• Treat this resource as a first-class artifact of the skill, not a generic chat response. Improve it when the skill's user-facing output needs to become richer.
• System resources compose OpenUI primitives and inherit SnappyChat tokens. Use ui_contract: branded in SKILL.md only for deliberate platform or client visuals.

Known Pitfalls

_(reclaimed ghost - no failures recorded in the new catalog yet.)_

Self-Test

1. [ ] Is this skill truly needed, or should I use an active neighbor?

<!-- kernel-ok: historical attribution for the PID-loader pattern. -->

Self-correcting loader (PID feedback)

This is the rule that makes loaders learn. Ported from snappy-kernel, where it demonstrably worked: the snappy-dom-cartographer skill mapped Skool admin UI once, every later ship-agent inherited the full map for free.

Before you finish, do two things:

1. Fix gaps (P - proportional). MANDATORY. If this loader didn't cover your case - if you had to read another file, run an undocumented command, work around a wrong selector, or discover a quirk - you MUST attempt an Edit to this AGENTS.md before you log.

• Default action: edit this file. Surgical. Add the missing line, table

row, or code example where it belongs. No restructuring.

• Only LOGGED is allowed when: the fix needs >10 lines, spans multiple

files, or requires a structural rewrite. In that case the state/regen/drain.sh queue picks it up asynchronously.

• "I didn't have time" / "it's minor" / "the next agent will figure it out"

are NOT valid reasons. Minor gaps compound - that's the whole point of this loop.

• Concrete example of a valid P-fix: discover agent-browser screenshot

takes path positionally not as --output <path>. One line in a table. Edit it in. Do not just log it.

• The goal: the next agent never has to leave the loader.

2. Log the result.

echo "[$(date -u +%FT%TZ)] contract-test: <what was missing or fixed> [FIXED|LOGGED]" >> state/log/loader-feedback.log

• FIXED = you patched this loader inline (P-fix).
• LOGGED = too large for inline; the PostToolUse enqueue + Stop-hook drain

will rewrite the loader from scratch on next session-end.

Do not skip this. Every agent run must leave the system better than it found it. The loader is the setpoint; you are the sensor; the gap is the error signal; closing the gap is the correction.