pi-dev 0.1.1 → 0.1.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-dev",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "An autonomous engineering skill framework for the pi runtime — built on Matt Pocock's skills.",
   "type": "module",
   "bin": {

package/skills/do/SKILL.md

@@ -40,6 +40,15 @@ The point: **one request → one finished outcome**, with as few user interrupti
 - Read docs/agents/{issue-tracker,triage-labels,domain}.md.
 - If GitHub is the tracker, run a 2-second readiness check (gh auth status, repo accessible). On fail, halt with fix commands.
 - If any preferences file's last-updated > 90 days, append a one-line refresh hint to the final summary.
+- **Taboo lint (1-shot, non-blocking).** After prefs are merged, run a quick drift probe and surface findings in the final summary (do not halt the flow):
+  ```bash
+  # handoff paths that the migration forbade
+  find docs/handoff .scratch/flow .handoff -type f 2>/dev/null | head
+  # post-migration commits that look like handoff writes
+  marker_date=$(grep -oE 'migrated: [0-9-]+' docs/agents/preferences.md 2>/dev/null | awk '{print $2}')
+  [ -n "$marker_date" ] && git log --since="$marker_date" --oneline --grep='handoff\|SESSION_' | head
+  ```
+  Any hit → add a "taboo drift" line to the final summary recommending `/migrate` re-run. Findings are advisory at this stage; `/migrate` owns the cleanup.
 - If the user's request hints at continuation ("이어서", "지난번", "where were we", "다시 시작"), invoke `/where` (optional). Otherwise skip it — the migration-enforced state-of-work channels (code / issues / prefs) are usually enough.
 ```
 

package/skills/migrate/SKILL.md

@@ -180,7 +180,14 @@ Wait for user OK. Show exact text being preserved or translated if user asks.
 
 In order:
 
-1. **Backup**: `mv` everything in ARCHIVE to `.archive/<date>-pre-migration/`. Add `.archive/` to `.gitignore` if not present.
+1. **Backup + handoff lockout**: `mv` everything in ARCHIVE to `.archive/$(date -u +%Y-%m-%d)-pre-migration/`. Add `.archive/` to `.gitignore` if not present. **Also append handoff-path lockouts** to `.gitignore` so they cannot silently come back:
+   ```
+   # post-migration: handoff systems are forbidden (see docs/agents/preferences.md taboos)
+   docs/handoff/
+   .scratch/flow/
+   .handoff/
+   ```
+   If the repo already gitignores these for a different reason, leave them — the rule still holds.
 2. **Setup docs**: invoke `/setup` if any of `docs/agents/{issue-tracker,triage-labels,domain}.md` missing.
 3. **Rewrite AGENTS.md** with the canonical skeleton:
    ```markdown
@@ -208,10 +215,12 @@ In order:
    ```
 4. **Sub-AGENTS.md**: if scoped `<subdir>/AGENTS.md` exists, leave it but strip duplicated process docs; preserve only hard rules specific to that subtree.
 5. **Onboard preferences**: invoke `/taste` in onboarding mode.
-6. **Mark migrated**: append to `docs/agents/preferences.md`:
-   ```
-   <!-- migrated: <ISO-date> by `/migrate` -->
+6. **Mark migrated**: append to `docs/agents/preferences.md` using the real current ISO date (shell-resolved, never hand-typed):
+   ```bash
+   printf '\n<!-- migrated: %s by `/migrate` -->\n' "$(date -u +%Y-%m-%d)" \
+     >> docs/agents/preferences.md
    ```
+   The marker literal must read `<!-- migrated: YYYY-MM-DD by \`/migrate\` -->`. Do not paste a future or rounded date — `/do`'s 90-day staleness check relies on this being accurate.
 7. **Print summary**: counts of preserved / translated / archived / written, plus any FYI items needing manual review.
 
 ### 6. Idempotency
@@ -220,6 +229,23 @@ This skill is safe to re-run. On second run:
 - If marker present and no drift detected → print "already migrated, no changes" and exit.
 - If drift detected (new handoff files appeared, AGENTS.md got a generic process section bolted on, etc.) → present a diff for those drifts only.
 
+**Drift probes** (run all on re-entry, regardless of marker):
+
+```bash
+# 1. handoff paths resurrected since migration
+find docs/handoff .scratch/flow .handoff -type f 2>/dev/null | head
+
+# 2. handoff-style commits after the migration marker
+marker_date=$(grep -oE 'migrated: [0-9-]+' docs/agents/preferences.md | awk '{print $2}')
+[ -n "$marker_date" ] && git log --since="$marker_date" --oneline --grep='handoff\|SESSION_' || true
+
+# 3. taboo labels still alive on the tracker (GitHub example)
+gh label list --json name --jq '.[].name' 2>/dev/null \
+  | grep -E '^(retro-action-item|process-audit|handoff)$' || true
+```
+
+Any non-empty output → surface as drift in the plan and offer to clean up (delete files, rename commits is N/A, archive labels via `gh label delete` after confirming zero usage). Do not silently ignore.
+
 ## When migration cannot proceed
 
 - User refuses to delete a competing rule file (CLAUDE.md vs AGENTS.md both alive) → migration stops, `/do` stays blocked. The decision must be made.

package/skills/to-issues/SKILL.md

@@ -55,7 +55,11 @@ For each approved slice, publish a new issue to the issue tracker. Use the issue
 
 Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
 
+**Every issue body MUST start with the AI disclaimer** (same wording as `/triage`). This is a hard requirement — no exceptions, including auto-generated slices. After writing the body, grep your own draft for the disclaimer string; if missing, do not publish.
+
 <issue-template>
+> *This was generated by AI during triage.*
+
 ## Parent
 
 A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).
@@ -78,4 +82,28 @@ Or "None - can start immediately" if no blockers.
 
 </issue-template>
 
+**Publishing pattern (GitHub).** Use `--body-file -` with a heredoc, never inline `--body "..."`, so the disclaimer and markdown structure survive shell quoting verbatim:
+
+```bash
+gh issue create \
+  --title "[Slice N] <title>" \
+  --label needs-triage \
+  --body-file - <<'EOF'
+> *This was generated by AI during triage.*
+
+## Parent
+#<parent>
+
+## What to build
+...
+EOF
+```
+
+After creation, immediately verify the disclaimer landed:
+
+```bash
+gh issue view <n> --json body --jq '.body' | head -1 | grep -q 'generated by AI' \
+  || echo "FAIL: disclaimer missing on #<n>"
+```
+
 Do NOT close or modify any parent issue.