#32

WS2 · Second-DS agnosticism run — shadcn/ui (HITL)

OpendieDeMiguelopened 5mo ago

What to build

HITL — the operator (Diego) answers the Phase-1 gate.

One full extraction run against shadcn/ui (public, MIT, already studied) to prove the extractor's improvements are generic by demonstration, not assertion. This is the second of the two agnosticism gates (the first is the lexical deny-list, #29).

  • Accept the extractor's default proposed slate at the Phase-1 gate (or prune — operator's call).
  • The produced skill is a test artifact: persist the run record (phase handoffs, produced skill, audit output) on a branch or scratch directory — do not install it on main.
  • Timing is free: any time before the extractor is declared done.
  • Zero extractor edits mid-run — a defect found during the run becomes a follow-up issue, so the run stays a clean measurement.

Spec: PRDs/PRD-workshop-quality-taste-and-truth.md (v6), WS2.7(b).

Acceptance criteria

  • The produced shadcn/ui skill passes produced-mode checks (check-skill-docs.sh exit 0).
  • The run record is persisted and linked from this issue.
  • No extractor files changed during the run; defects (if any) filed as follow-ups.

Blocked by

  • #27 (claims-file contract)
  • #28 (public-sources input model)
  • #29 (lexical deny-list)
  • #30 (full-coverage rule)

Activity

2
dieDeMiguel5mo ago

Loop guard — HITL, do not pick in AFK (2026-06-12)

This is a human-in-the-loop ticket and must not be picked by the AFK loop. Skip it. The active AFK queue is the primer-react extraction chain #41 → #42 → #43.

dieDeMiguel5mo ago

On hold — paused while the primer-react regeneration run (#40 → #41 → #42 → #43) executes through the corrected, registry-scoped meta-skill in the .claude/worktrees/dryrun-20-improved-metaskill copy.

The AFK Ralph loop (run-claude-afk-signed.sh --source github-issues) fetches all open issues and has no label filter, so this shadcn/ui agnosticism run is held to keep the loop focused on the primer-react phases. AFK loop: do not pick this issue up until the primer-react regeneration lands.

Resume once #40's acceptance is ticked off. No work lost — this is a scheduling hold, not a scope change.