devlyn-cli 3.3.1 → 4.0.1

package/config/skills/devlyn-queue/scripts/append.py

@@ -0,0 +1,94 @@
+#!/usr/bin/env python3
+"""Append one normalized pending intent to the project queue."""
+
+import argparse
+import os
+import re
+import sys
+from contextlib import contextmanager
+from pathlib import Path
+
+
+QUEUE_PATH = Path("docs/specs/queue.md")
+LOCK_PATH = Path(".devlyn/queue.lock")
+# Each `add` writes its own handoff file, so two adds never consume each other's intent.
+HANDOFF = re.compile(r"\.devlyn/queue-intent-[A-Za-z0-9._-]+\.txt")
+MINIMAL_HEADER = b"# Intent Queue\n\n"
+
+
+@contextmanager
+def queue_lock():
+    """One writer at a time across processes, from creating the queue to the append."""
+    LOCK_PATH.parent.mkdir(parents=True, exist_ok=True)
+    fd = os.open(LOCK_PATH, os.O_RDWR | os.O_CREAT, 0o644)
+    try:
+        if os.name == "nt":
+            import msvcrt
+
+            # The CRT locks bytes that exist; give a new lock file its one byte.
+            if os.fstat(fd).st_size == 0:
+                os.write(fd, b"\0")
+            os.lseek(fd, 0, os.SEEK_SET)
+            msvcrt.locking(fd, msvcrt.LK_LOCK, 1)
+            try:
+                yield
+            finally:
+                os.lseek(fd, 0, os.SEEK_SET)
+                msvcrt.locking(fd, msvcrt.LK_UNLCK, 1)
+        else:
+            import fcntl
+
+            fcntl.flock(fd, fcntl.LOCK_EX)
+            yield
+    finally:
+        os.close(fd)
+
+
+def append_intent(queue_path, intent):
+    normalized = " ".join(intent.split())
+    if not normalized:
+        raise ValueError("intent must contain non-whitespace text")
+    item = f"- [ ] {normalized}\n".encode("utf-8")
+
+    with queue_lock():
+        if not queue_path.exists():
+            queue_path.parent.mkdir(parents=True, exist_ok=True)
+            queue_path.write_bytes(MINIMAL_HEADER + item)
+            return
+
+        with queue_path.open("rb") as queue:
+            queue.seek(0, 2)
+            size = queue.tell()
+            if size:
+                queue.seek(-1, 2)
+                ends_with_newline = queue.read(1) == b"\n"
+            else:
+                ends_with_newline = True
+
+        prefix = b"" if ends_with_newline else b"\n"
+        with queue_path.open("ab") as queue:
+            queue.write(prefix + item)
+
+
+def main(argv=None):
+    parser = argparse.ArgumentParser(
+        description="Append one pending intent at the physical end of docs/specs/queue.md."
+    )
+    parser.add_argument("handoff", type=Path, help=".devlyn/queue-intent-<unique>.txt, relative to the project root")
+    args = parser.parse_args(argv)
+    if not HANDOFF.fullmatch(args.handoff.as_posix()):
+        parser.error(f"handoff must be .devlyn/queue-intent-<unique>.txt: {args.handoff}")
+    try:
+        try:
+            intent = args.handoff.read_text(encoding="utf-8")
+        finally:
+            args.handoff.unlink(missing_ok=True)
+        append_intent(QUEUE_PATH, intent)
+    except (OSError, UnicodeError, ValueError) as error:
+        print(f"queue add failed: {error}", file=sys.stderr)
+        return 1
+    return 0
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

package/config/skills/{devlyn:resolve → devlyn-resolve}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: devlyn:resolve
+name: devlyn-resolve
 description: Default to direct work after inspecting scope and verification, including bounded multi-file changes. Use full resolve for explicit resolve/spec-mode requests, queue drains, or concrete interacting requirements or verification too complex for the current context. Domain labels, file count, spec documents and quoted skill paths alone do not trigger it. Investigate or clarify missing intent/access first. Explicit small resolve retains all phases and independent verification. Verify dual-judge is default-when-available.
 ---
 
@@ -28,23 +28,42 @@ Every phase applies Subtractive-first / Goal-locked / No-workaround / Evidence,
 </harness_principles>
 
 <runtime_paths>
-Resolve shared scripts from this skill's installed directory, never from the project cwd. At PHASE 0, before any phase command:
-
-```bash
-DEVLYN_SKILL_DIR="${CLAUDE_SKILL_DIR:-__DEVLYN_SKILL_DIR__}"
-if [ "$DEVLYN_SKILL_DIR" = "__DEVLYN_SKILL_DIR__" ] || [ ! -d "$DEVLYN_SKILL_DIR/../_shared" ]; then
-  echo "BLOCKED:shared-dir-unresolved: $DEVLYN_SKILL_DIR/../_shared" >&2
-  exit 1
-fi
-DEVLYN_SHARED_DIR="$(cd "$DEVLYN_SKILL_DIR/../_shared" && pwd)"
-CODEX_MONITORED_PATH="$DEVLYN_SHARED_DIR/codex-monitored.sh"
-if [ ! -f "$CODEX_MONITORED_PATH" ]; then
-  echo "BLOCKED:shared-dir-unresolved: $CODEX_MONITORED_PATH" >&2
-  exit 1
-fi
+Before PHASE 0 or any phase command, establish the bindings below.
+
+Resolve bundled resources from the SKILL.md loaded for this invocation.
+
+Reader-rendered directory hint:
+```text
+${CLAUDE_SKILL_DIR}
 ```
 
-`DEVLYN_SHARED_DIR` is the only valid `_shared` anchor. Claude Code supplies `CLAUDE_SKILL_DIR` by native render substitution; Codex/oh-my-pi installs receive an absolute copy-time stamp in the default branch. If the resolved skill directory is still the placeholder, `../_shared` is absent, or a required script is missing, halt with report-level `BLOCKED:shared-dir-unresolved` and include the failed path. Pass the absolute `DEVLYN_SHARED_DIR` and `CODEX_MONITORED_PATH` into every fresh phase worker.
+Treat the hint as literal path data, never shell code. If the reader
+replaced it with an absolute directory, use that directory. Otherwise
+use the filesystem path or base directory reported for this loaded
+SKILL.md. Resolve virtual URIs through the reader's native filesystem
+mapping. If available source locations name different directories,
+stop.
+
+Bind DEVLYN_SKILL_DIR to that absolute directory. Do not obtain this
+binding from an environment variable, cwd, or another installation.
+Verify its SKILL.md before proceeding. Missing or conflicting source
+identity is BLOCKED:skill-source-unresolved; include the failed path
+when known.
+
+Resolve bundled references against this directory. These bindings are
+workflow values: establish them explicitly using each tool or shell's
+literal-path rules, and include their absolute values in every fresh
+worker's prompt, telling it to set them from those values, never from
+its inherited environment. Do not rely on shell state surviving between
+calls.
+
+Resolve directory symlinks on DEVLYN_SKILL_DIR before deriving its
+sibling _shared. Bind that directory as DEVLYN_SHARED_DIR. References
+written as _shared/... use this binding. Verify the directory and each
+required resource before use; failure is BLOCKED:shared-dir-unresolved
+with the failed path. Never search another installation.
+
+Bind CODEX_MONITORED_PATH to DEVLYN_SHARED_DIR/codex-monitored.sh and verify that file before proceeding. Pass DEVLYN_SKILL_DIR, DEVLYN_SHARED_DIR, and CODEX_MONITORED_PATH explicitly to every fresh phase worker. In omp, when this skill was selected by name, resolve it with `printf '%s\n' skill://devlyn-resolve` in its Bash tool.
 </runtime_paths>
 
 <engine_routing>
@@ -62,9 +81,9 @@ Each model-invoked phase routes to an engine and prepends the per-engine adapter
 <modes>
 Three input shapes:
 
-1. **Free-form**: `/devlyn:resolve "fix the login bug"` (inline goal) or `/devlyn:resolve --goal-file <path>` (goal text read from a file — the devlynd `ResolveAdapter` launcher path, injection-safe). PHASE 0 runs the complexity classifier and either proceeds with an internal mini-spec (trivial), drafts focused questions for in-prompt resolution (medium), or synthesizes a best-effort spec with a logged `## Assumptions` block (large; zero-scope-signal goals halt). No mid-pipeline prompts in any branch.
-2. **Spec**: `/devlyn:resolve --spec docs/roadmap/phase-N/X.md`. Supplied specs and expected files are read-only inside resolve. Stage verification commands from sibling `spec.expected.json`; if absent, use the legacy `## Verification` JSON block.
-3. **Verify-only**: `/devlyn:resolve --verify-only <diff-or-PR-ref> --spec <path>`. Skips PHASE 1-4. Runs PHASE 5 (VERIFY) on the supplied diff against the spec.
+1. **Free-form**: `/devlyn-resolve "fix the login bug"` (inline goal) or `/devlyn-resolve --goal-file <path>` (goal text read from a file — the devlynd `ResolveAdapter` launcher path, injection-safe). PHASE 0 runs the complexity classifier and either proceeds with an internal mini-spec (trivial), drafts focused questions for in-prompt resolution (medium), or synthesizes a best-effort spec with a logged `## Assumptions` block (large; zero-scope-signal goals halt). No mid-pipeline prompts in any branch.
+2. **Spec**: `/devlyn-resolve --spec docs/roadmap/phase-N/X.md`. Supplied specs and expected files are read-only inside resolve. Stage verification commands from sibling `spec.expected.json`; if absent, use the legacy `## Verification` JSON block.
+3. **Verify-only**: `/devlyn-resolve --verify-only <diff-or-PR-ref> --spec <path>`. Skips PHASE 1-4. Runs PHASE 5 (VERIFY) on the supplied diff against the spec.
 </modes>
 
 <post_implement_invariant>

package/config/skills/{devlyn:resolve → devlyn-resolve}/references/free-form-mode.md

@@ -1,6 +1,6 @@
 # Free-form mode — complexity classifier
 
-When `/devlyn:resolve` is invoked with a free-form goal (no `--spec`) — whether the goal is the inline positional text or the content of `--goal-file <path>` (PHASE 0 resolves `goal_text` from either source before classifying) — PHASE 0 runs this classifier to set `state.complexity ∈ {trivial, medium, large}` and either proceeds with an internal mini-spec, drafts focused questions for in-prompt resolution, synthesizes a best-effort spec with logged assumptions, or halts zero-scope-signal goals with `/devlyn:ideate` guidance.
+When `/devlyn-resolve` is invoked with a free-form goal (no `--spec`) — whether the goal is the inline positional text or the content of `--goal-file <path>` (PHASE 0 resolves `goal_text` from either source before classifying) — PHASE 0 runs this classifier to set `state.complexity ∈ {trivial, medium, large}` and either proceeds with an internal mini-spec, drafts focused questions for in-prompt resolution, synthesizes a best-effort spec with logged assumptions, or halts zero-scope-signal goals with `/devlyn-ideate` guidance.
 
 The classifier is rules-based / deterministic — not an LLM judgment call. Decision rules below.
 
@@ -49,7 +49,7 @@ Conditions (any one):
 - The goal mentions a new feature whose surface area requires design decisions the harness cannot make from a one-shot prompt.
 
 Action:
-- Default: synthesize a best-effort spec from the goal with an explicit `## Assumptions` block (every assumption scope-narrowing and reversible — when in doubt, narrower); log `recommend: /devlyn:ideate first` in `.devlyn/criteria.generated.md` AND the final report; proceed to PHASE 1; the final report flags every assumption for user review.
+- Default: synthesize a best-effort spec from the goal with an explicit `## Assumptions` block (every assumption scope-narrowing and reversible — when in doubt, narrower); log `recommend: /devlyn-ideate first` in `.devlyn/criteria.generated.md` AND the final report; proceed to PHASE 1; the final report flags every assumption for user review.
 - Zero-signal exception: if the large classification includes `file_scope_signals == 0` (classifier cannot pick scope), halt with terminal verdict `BLOCKED:large-needs-ideation` — assumptions there would be scope-invention, not narrowing.
 
 ## Anti-pattern: drift to LLM judgment
@@ -63,7 +63,7 @@ When the rules are silent (rare — pathological goal text), default to `medium`
 The internal mini-spec written for trivial / medium / large-assumptions paths must satisfy:
 
 - `## Requirements` non-empty, each bullet testable (CLI command, test command, observable file change).
-- For executable generated verification, put one fenced `json` object with `verification_commands` inside the sentinel-marked `## Verification` section. Generated mode reads this inline carrier, not a sibling file. Follow `../../devlyn:ideate/references/spec-template.md` § "Sibling file: `spec.expected.json`" for constraint coverage, diff scope and violating/allowed controls, but express those checks as executable `verification_commands`; sibling-only fields such as `required_files` and `forbidden_patterns` are rejected inline. Preserve uncovered semantics as source-review obligations.
+- For executable generated verification, put one fenced `json` object with `verification_commands` inside the sentinel-marked `## Verification` section. Generated mode reads this inline carrier, not a sibling file. Follow `../../devlyn-ideate/references/spec-template.md` § "Sibling file: `spec.expected.json`" for constraint coverage, diff scope and violating/allowed controls, but express those checks as executable `verification_commands`; sibling-only fields such as `required_files` and `forbidden_patterns` are rejected inline. Preserve uncovered semantics as source-review obligations.
 - `## Verification` is preceded by a `<!-- devlyn:verification -->` sentinel on its own line directly above the heading — the machine locator `spec-verify-check.py` uses; the heading text itself is decorative and may be any language. When all Requirements are pure-design with no runnable acceptance check, put `{"pure_design": true, "verification_commands": []}` in the fenced `json` block and retain semantic source-review obligations. This explicit declaration is required; a missing block, an unmarked empty list, or `pure_design: true` with commands is invalid.
 - Free-form mode mini-specs are written to `.devlyn/criteria.generated.md` (not to a roadmap path) — this is run-scoped artifact, not a documented spec.
 - After writing `.devlyn/criteria.generated.md`, set `state.source.type = "generated"`, `state.source.spec_path = null`, `state.source.spec_sha256 = null`, `state.source.criteria_path = ".devlyn/criteria.generated.md"`, and `state.source.criteria_sha256` to the raw-byte SHA-256 of the generated criteria file. Downstream PLAN/IMPLEMENT/VERIFY phases and `spec-verify-check.py --include-risk-probes` depend on this pointer; do not rely on the file existing by convention.

package/config/skills/{devlyn:resolve → devlyn-resolve}/references/outer-loop.md

@@ -1,6 +1,6 @@
 # Outer-loop commit boundary
 
-A full `/devlyn:resolve` run starts only from committed owner inputs. Keep each
+A full `/devlyn-resolve` run starts only from committed owner inputs. Keep each
 commit scoped: no unrelated paths or queue-item changes.
 
 1. Before task writes, the outer owner allocates an absent task branch per

package/config/skills/{devlyn:resolve → devlyn-resolve}/references/state-schema.md

@@ -1,6 +1,6 @@
 # pipeline.state.json schema
 
-Single authoritative verdict source for `/devlyn:resolve`. The orchestrator branches on `state.phases.<name>.verdict` directly — never parses `.devlyn/*.findings.jsonl` for routing. Living document; bump `version` on a breaking change.
+Single authoritative verdict source for `/devlyn-resolve`. The orchestrator branches on `state.phases.<name>.verdict` directly — never parses `.devlyn/*.findings.jsonl` for routing. Living document; bump `version` on a breaking change.
 
 ## Top-level shape
 

package/config/skills/{devlyn:resolve → devlyn-resolve}/references/task-completion.md

@@ -7,8 +7,15 @@ authorized by the task scope; no additional approval ceremony is required.
 
 ## Allocate before work
 
-Use the installed `_shared/task-complete.py` from the anchor checkout,
-before committing owner inputs or starting direct/full work:
+Use the caller's DEVLYN_SHARED_DIR. When this reference is opened
+directly, derive that binding from ../../_shared relative to this
+reference's reader-supplied containing directory, resolving directory
+symlinks first. Missing source identity is
+BLOCKED:skill-source-unresolved; a missing task-complete.py is
+BLOCKED:shared-dir-unresolved. Never select another installation.
+
+Run the bound task-complete.py before committing owner inputs or
+starting direct/full work:
 
 ```sh
 python3 "$DEVLYN_SHARED_DIR/task-complete.py" allocate --repo . \

package/config/templates/prompt-templates.md

@@ -23,7 +23,7 @@ Start with the minimum viable solution, then improve if time allows.
 
 ## Debugging
 
-For systematic debugging, use `/devlyn:resolve [issue description]` which includes:
+For systematic debugging, use `/devlyn-resolve [issue description]` which includes:
 - Code path mapping
 - Hypothesis-driven analysis
 - Test-driven fix validation
@@ -61,7 +61,7 @@ have working, tested code ready for PR.
 For complex bugs that need autonomous resolution:
 
 ```
-/devlyn:resolve [bug description]
+/devlyn-resolve [bug description]
 
 After analysis, implement the fix autonomously:
 - Write failing test first

package/optional-skills/better-auth-setup/SKILL.md

@@ -30,13 +30,19 @@ The setup produces a dual-auth system: session cookies for browser users and API
 
 Read these when each step directs you to them:
 
-- `${CLAUDE_SKILL_DIR}/references/schema.md` — Complete Drizzle schema (auth, org, API key tables)
-- `${CLAUDE_SKILL_DIR}/references/middleware.md` — Auth middleware, tenant context, types, error handler
-- `${CLAUDE_SKILL_DIR}/references/api-keys.md` — Key generation, CRUD routes, security patterns
-- `${CLAUDE_SKILL_DIR}/references/config-and-entry.md` — Env config, error types, entry point wiring
-- `${CLAUDE_SKILL_DIR}/references/testing.md` — Test preload, seed factory, integration patterns
-- `${CLAUDE_SKILL_DIR}/references/proxy-setup.md` — Reverse proxy architecture, forwarding headers, OAuth callback routing
-- `${CLAUDE_SKILL_DIR}/references/proxy-gotchas.md` — Proxy-specific troubleshooting (redirect_uri_mismatch, state_mismatch, cookie prefix issues)
+Resolve the bundled references/... paths below against the directory
+containing the SKILL.md loaded for this invocation, using its opened
+path, reader-reported base directory, or native URI mapping. Never
+resolve them against cwd or another installation. Missing source
+identity is BLOCKED:skill-source-unresolved.
+
+- `references/schema.md` — Complete Drizzle schema (auth, org, API key tables)
+- `references/middleware.md` — Auth middleware, tenant context, types, error handler
+- `references/api-keys.md` — Key generation, CRUD routes, security patterns
+- `references/config-and-entry.md` — Env config, error types, entry point wiring
+- `references/testing.md` — Test preload, seed factory, integration patterns
+- `references/proxy-setup.md` — Reverse proxy architecture, forwarding headers, OAuth callback routing
+- `references/proxy-gotchas.md` — Proxy-specific troubleshooting (redirect_uri_mismatch, state_mismatch, cookie prefix issues)
 
 ## Handling Input
 
@@ -86,7 +92,7 @@ Generate the auth secret immediately (do not use a placeholder):
 bunx @better-auth/cli@latest secret
 ```
 
-Read `${CLAUDE_SKILL_DIR}/references/config-and-entry.md` for the complete Zod config implementation. Key env vars:
+Read `references/config-and-entry.md` for the complete Zod config implementation. Key env vars:
 
 | Variable | Required | Purpose |
 |----------|----------|---------|
@@ -104,7 +110,7 @@ Read `${CLAUDE_SKILL_DIR}/references/config-and-entry.md` for the complete Zod c
 **Entry:** Config validated at startup.
 **Exit:** Migration applied, tables created in PostgreSQL.
 
-Read `${CLAUDE_SKILL_DIR}/references/schema.md` for the complete schema. Key decisions:
+Read `references/schema.md` for the complete schema. Key decisions:
 
 - Use **plural table names** (`users`, `sessions`) — mapped to Better Auth's singular models in Step 3
 - Use **UUIDs** for all primary keys
@@ -284,7 +290,7 @@ authRoutes.on(["POST", "GET"], "/*", (c) => auth.handler(c.req.raw));
 **Entry:** Auth routes mounted.
 **Exit:** `src/middleware/auth.ts` validates API keys and session cookies.
 
-Read `${CLAUDE_SKILL_DIR}/references/middleware.md` for the complete implementation. The middleware:
+Read `references/middleware.md` for the complete implementation. The middleware:
 - Detects API keys via `Authorization: Bearer pyx_...` prefix
 - Validates via SHA-256 hash lookup + revocation + expiration checks
 - Falls back to Better Auth session cookie validation
@@ -299,7 +305,7 @@ Read `${CLAUDE_SKILL_DIR}/references/middleware.md` for the complete implementat
 **Entry:** Auth middleware populates `AuthContext` on the request.
 **Exit:** `src/middleware/tenant-context.ts` resolves org and plan.
 
-Read `${CLAUDE_SKILL_DIR}/references/middleware.md` for the implementation. Key behaviors:
+Read `references/middleware.md` for the implementation. Key behaviors:
 - API key auth: org already resolved from the key's project, just fetches plan
 - Session auth: looks up user's most recent org membership
 - Uses distinct error code `no_organization` (not generic `forbidden`) so the frontend can show "Create your first organization" instead of "Access denied"
@@ -311,7 +317,7 @@ Read `${CLAUDE_SKILL_DIR}/references/middleware.md` for the implementation. Key
 **Entry:** Middleware needs error classes to throw.
 **Exit:** `src/lib/errors.ts` with `AppError` hierarchy, `src/middleware/error-handler.ts`.
 
-Read `${CLAUDE_SKILL_DIR}/references/config-and-entry.md` for the complete error hierarchy and handler. Every error has a distinct `code` field for frontend differentiation:
+Read `references/config-and-entry.md` for the complete error hierarchy and handler. Every error has a distinct `code` field for frontend differentiation:
 
 | Error Class | Code | Status |
 |-------------|------|--------|
@@ -328,7 +334,7 @@ Read `${CLAUDE_SKILL_DIR}/references/config-and-entry.md` for the complete error
 **Entry:** All middleware and routes implemented.
 **Exit:** `src/index.ts` with correct middleware ordering.
 
-Read `${CLAUDE_SKILL_DIR}/references/config-and-entry.md` for the complete entry point. The middleware order is:
+Read `references/config-and-entry.md` for the complete entry point. The middleware order is:
 
 1. **Request ID** — first, so error handler can include it in responses
 2. **Security Headers** — HSTS (production), X-Frame-Options
@@ -348,7 +354,7 @@ CORS before auth routes is non-negotiable. If registered after, preflight OPTION
 **Entry:** Application fully functional.
 **Exit:** Test preload, seed factory, integration app, cleanup utilities.
 
-Read `${CLAUDE_SKILL_DIR}/references/testing.md` for the complete test setup. Essential components:
+Read `references/testing.md` for the complete test setup. Essential components:
 
 1. **Test preload** (`bunfig.toml` + `setup.ts`) — clears `RESEND_API_KEY`, bridges `TEST_DATABASE_URL`
 2. **Seed factory** (`seedTestData()`) — creates full tenant hierarchy with unique slugs
@@ -413,7 +419,7 @@ If any item fails, fix the root cause before proceeding.
 
 ## API Key System
 
-For the complete custom API key implementation (generation, validation, CRUD routes), read `${CLAUDE_SKILL_DIR}/references/api-keys.md`.
+For the complete custom API key implementation (generation, validation, CRUD routes), read `references/api-keys.md`.
 
 Summary:
 - **Format**: `pyx_` prefix + 32 random bytes base62-encoded (~50 chars)
@@ -447,7 +453,7 @@ Always append a unique suffix (UUID slice or timestamp) to prevent collisions.
 
 ## Proxy Architecture (Steps 12-14)
 
-These steps apply when the frontend is a separate application that proxies auth requests to the backend. Read `${CLAUDE_SKILL_DIR}/references/proxy-setup.md` for the complete guide with code examples.
+These steps apply when the frontend is a separate application that proxies auth requests to the backend. Read `references/proxy-setup.md` for the complete guide with code examples.
 
 ### Step 12: Configure Dynamic baseURL on Backend
 
@@ -499,7 +505,7 @@ socialProviders: {
 **Entry:** Backend uses `allowedHosts` with `trustedProxyHeaders`.
 **Exit:** Frontend proxies auth requests and OAuth callbacks correctly.
 
-The frontend proxy must do three things. Read `${CLAUDE_SKILL_DIR}/references/proxy-setup.md` for complete code.
+The frontend proxy must do three things. Read `references/proxy-setup.md` for complete code.
 
 #### 13a. Create two proxy routes
 
@@ -592,7 +598,7 @@ curl -s -X POST "https://your-frontend.com/api/auth/sign-in/social" \
 
 Expected: `redirect_uri: https://your-frontend.com/auth/callback/google`
 
-For detailed troubleshooting of proxy-specific failures, read `${CLAUDE_SKILL_DIR}/references/proxy-gotchas.md`.
+For detailed troubleshooting of proxy-specific failures, read `references/proxy-gotchas.md`.
 
 ---
 

package/optional-skills/{devlyn:pencil-pull → devlyn-pencil-pull}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: devlyn:pencil-pull
+name: devlyn-pencil-pull
 description: Pull Pencil designs into code with exact visual fidelity.
 ---
 

package/optional-skills/{devlyn:pencil-push → devlyn-pencil-push}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: devlyn:pencil-push
+name: devlyn-pencil-push
 description: Push codebase UI to Pencil canvas for design sync.
 ---
 

package/optional-skills/{devlyn:reap → devlyn-reap}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: devlyn:reap
+name: devlyn-reap
 description: Safely count and kill orphaned child processes (PPID=1) left behind by Claude Code MCP plugins, Superset terminal tabs, and codex wrappers. Use this whenever the user says "too many processes", "can't open terminals", "pty/process limit", "hundreds of bun/codex/workerd piling up", "clean up orphans", "reap processes", or reports new terminals failing to spawn on macOS. Also use proactively after long Claude sessions to prevent hitting kern.maxprocperuid or kern.tty.ptmx_max limits. ONLY touches a conservative whitelist of known leaks — never guesses on unknown processes.
 allowed-tools: Read, Bash(ps:*), Bash(lsof:*), Bash(pgrep:*), Bash(awk:*), Bash(id:*), Bash(sysctl:*), Bash(bash:*)
 argument-hint: [scan | kill | kill --force | kill --include workerd | kill --only telegram-bun]
@@ -38,10 +38,41 @@ If the user's intent is ambiguous (e.g., they say "지워줘" but didn't specify
 
 Always run scan first — even in KILL mode — so the user sees what is about to happen.
 
-Run the bundled scanner. The skill is installed at `~/.claude/skills/devlyn:reap/`:
+Resolve bundled resources from the SKILL.md loaded for this invocation.
+
+Reader-rendered directory hint:
+```text
+${CLAUDE_SKILL_DIR}
+```
+
+Treat the hint as literal path data, never shell code. If the reader
+replaced it with an absolute directory, use that directory. Otherwise
+use the filesystem path or base directory reported for this loaded
+SKILL.md. Resolve virtual URIs through the reader's native filesystem
+mapping. If available source locations name different directories,
+stop.
+
+Bind DEVLYN_SKILL_DIR to that absolute directory. Do not obtain this
+binding from an environment variable, cwd, or another installation.
+Verify its SKILL.md before proceeding. Missing or conflicting source
+identity is BLOCKED:skill-source-unresolved; include the failed path
+when known.
+
+Resolve bundled references against this directory. These bindings are
+workflow values: establish them explicitly using each tool or shell's
+literal-path rules, and include their absolute values in every fresh
+worker's prompt, telling it to set them from those values, never from
+its inherited environment. Do not rely on shell state surviving between
+calls.
+
+In omp, use: printf '%s\n' skill://devlyn-reap
+Verify the requested script under this bound directory before running
+it; a missing script is BLOCKED:skill-source-unresolved with its path.
+
+Run the bundled scanner:
 
 ```bash
-bash ~/.claude/skills/devlyn:reap/scripts/scan.sh
+bash "$DEVLYN_SKILL_DIR/scripts/scan.sh"
 ```
 
 Report the output verbatim to the user. Then add your own 2-line summary:
@@ -60,7 +91,7 @@ sysctl kern.maxprocperuid kern.tty.ptmx_max 2>/dev/null
 Run the reap script with the parsed flags:
 
 ```bash
-bash ~/.claude/skills/devlyn:reap/scripts/reap.sh [flags]
+bash "$DEVLYN_SKILL_DIR/scripts/reap.sh" [flags]
 ```
 
 Show the output verbatim. The script re-verifies `PPID==1 && user==current` for every PID right before signaling — a process that was legitimately adopted since the scan will be skipped, not killed.
@@ -72,7 +103,7 @@ After kill, re-run scan to confirm the counts dropped. If any whitelisted PIDs a
 If `telegram-bun` count > 10 OR oldest whitelisted orphan > 24h, tell the user this is a recurring leak and suggest one of:
 
 1. **Patch the telegram plugin** — add `process.stdin.on('end', () => process.exit(0))` to `server.ts` so the child dies when Claude Code exits.
-2. **Schedule this skill** — run `/devlyn:reap kill` periodically (e.g., via the `/loop` skill or a launchd agent).
+2. **Schedule this skill** — run `/devlyn-reap kill` periodically (e.g., via the `/loop` skill or a launchd agent).
 3. **Update Superset** — newer versions may SIGTERM process groups on tab close.
 
 Do NOT apply these automatically. Recommend and let the user choose.

package/optional-skills/{devlyn:reap → devlyn-reap}/scripts/reap.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# devlyn:reap — kill orphan processes from safe whitelist categories.
+# devlyn-reap — kill orphan processes from safe whitelist categories.
 # Verifies PPID==1 and user-ownership AGAIN at kill time to avoid racing a
 # legitimately-reparented process. Unknown orphans are never killed.
 #

package/optional-skills/{devlyn:reap → devlyn-reap}/scripts/scan.sh

@@ -1,5 +1,5 @@
 #!/usr/bin/env bash
-# devlyn:reap — scan orphan processes by safe-to-kill category.
+# devlyn-reap — scan orphan processes by safe-to-kill category.
 # Read-only. Never kills anything. Always exits 0 on success.
 #
 # Output format: one TSV line per category with

package/optional-skills/dokkit/COMMANDS.md

@@ -187,12 +187,12 @@ File path to the template document (DOCX or HWPX).
 
 **Phase 3 — Source Images**:
 7. **Cell-level images**: For each `field_type: "image"` with `image_file: null` and `image_type: "figure"`:
-   - Run: `python .claude/skills/dokkit/scripts/source_images.py generate --prompt "<prompt>" --preset technical_illustration --output-dir .dokkit/images/ --project-dir . --lang ko`
+   - Run: `python "$DEVLYN_SKILL_DIR/scripts/source_images.py" generate --prompt "<prompt>" --preset technical_illustration --output-dir .dokkit/images/ --project-dir . --lang ko`
    - Parse `__RESULT__` JSON, update `analysis.json`
    - Skip photo/signature types (require user-provided files)
    - Default `--lang ko` (Korean only). Override with user instruction if needed.
 8. **Section content images**: For each `image_opportunities` entry with `status: "pending"`:
-   - Run: `python .claude/skills/dokkit/scripts/source_images.py generate --prompt "<generation_prompt>" --preset <preset> --output-dir .dokkit/images/ --project-dir . --lang ko`
+   - Run: `python "$DEVLYN_SKILL_DIR/scripts/source_images.py" generate --prompt "<generation_prompt>" --preset <preset> --output-dir .dokkit/images/ --project-dir . --lang ko`
    - On failure: set `status: "skipped"`, log reason
    - Use `--lang ko+en` if the content contains technical terms that benefit from English (e.g., architecture diagrams with API names).
 9. Report: "Sourced X/Y images"
@@ -272,8 +272,8 @@ File path to the template document (DOCX or HWPX).
 > "Analyze the template at `<path>`. Detect all fillable fields INCLUDING image fields. Map to sources. Write `analysis.json`."
 
 **Image sourcing** (inline, between agents):
-- **Pass A — Cell-level**: For `field_type: "image"` with `image_file: null` and `image_type: "figure"`, run `python .claude/skills/dokkit/scripts/source_images.py generate --prompt "..." --preset ... --output-dir .dokkit/images/ --project-dir . --lang ko`
-- **Pass B — Section content**: For `image_opportunities` with `status: "pending"`, run `python .claude/skills/dokkit/scripts/source_images.py generate --prompt "..." --preset ... --output-dir .dokkit/images/ --project-dir . --lang ko`
+- **Pass A — Cell-level**: For `field_type: "image"` with `image_file: null` and `image_type: "figure"`, run `python "$DEVLYN_SKILL_DIR/scripts/source_images.py" generate --prompt "..." --preset ... --output-dir .dokkit/images/ --project-dir . --lang ko`
+- **Pass B — Section content**: For `image_opportunities` with `status: "pending"`, run `python "$DEVLYN_SKILL_DIR/scripts/source_images.py" generate --prompt "..." --preset ... --output-dir .dokkit/images/ --project-dir . --lang ko`
 - Default language is `ko` (Korean only). Use `--lang ko+en` for mixed content, or `--lang en` for English-only.
 
 **Then**: Spawn the dokkit-filler agent in fill mode:

package/optional-skills/dokkit/EXPORT.md

@@ -41,8 +41,8 @@ def compile_hwpx(work_dir: str, output_path: str):
 
 ### Scripts
 ```bash
-python .claude/skills/dokkit/scripts/compile_hwpx.py <work_dir> <output.hwpx>
-python .claude/skills/dokkit/scripts/export_pdf.py <input> <output.pdf>
+python "$DEVLYN_SKILL_DIR/scripts/compile_hwpx.py" <work_dir> <output.hwpx>
+python "$DEVLYN_SKILL_DIR/scripts/export_pdf.py" <input> <output.pdf>
 ```
 
 ## PDF Conversion
@@ -54,7 +54,7 @@ soffice --headless --convert-to pdf --outdir <output_dir> <input_file>
 
 ### Using Python Script
 ```bash
-python .claude/skills/dokkit/scripts/export_pdf.py <input> <output.pdf>
+python "$DEVLYN_SKILL_DIR/scripts/export_pdf.py" <input> <output.pdf>
 ```
 
 ## Cross-Format Conversion

package/optional-skills/dokkit/FILLING.md

@@ -15,24 +15,24 @@ Field detection, matching strategies, and surgical XML editing rules for the dok
 
 ### DOCX Field Detection
 ```bash
-python .claude/skills/dokkit/scripts/detect_fields.py <document.xml>
+python "$DEVLYN_SKILL_DIR/scripts/detect_fields.py" <document.xml>
 ```
 Outputs JSON array of detected fields with labels, types, and XML paths.
 
 ### HWPX Field Detection
 ```bash
-python .claude/skills/dokkit/scripts/detect_fields_hwpx.py <section.xml>
+python "$DEVLYN_SKILL_DIR/scripts/detect_fields_hwpx.py" <section.xml>
 ```
 Same output format, adapted for HWPX XML structure.
 
 ### DOCX Validation
 ```bash
-python .claude/skills/dokkit/scripts/validate_docx.py <work_dir>
+python "$DEVLYN_SKILL_DIR/scripts/validate_docx.py" <work_dir>
 ```
 
 ### HWPX Validation
 ```bash
-python .claude/skills/dokkit/scripts/validate_hwpx.py <work_dir>
+python "$DEVLYN_SKILL_DIR/scripts/validate_hwpx.py" <work_dir>
 ```
 
 ## Matching Strategy

package/optional-skills/dokkit/IMAGE-SOURCING.md

@@ -25,7 +25,7 @@ Via `/dokkit modify "use <file>"`:
 
 ### 3. AI Generation
 ```bash
-python .claude/skills/dokkit/scripts/source_images.py generate \
+python "$DEVLYN_SKILL_DIR/scripts/source_images.py" generate \
   --prompt "인포그래픽: AI 감정 케어 플랫폼 4단계 로드맵" \
   --preset infographic \
   --output-dir .dokkit/images/ \
@@ -61,7 +61,7 @@ Use `--aspect-ratio 16:9` to override. Use `--no-enhance` to skip preset style i
 
 ### 4. Web Search
 ```bash
-python .claude/skills/dokkit/scripts/source_images.py search \
+python "$DEVLYN_SKILL_DIR/scripts/source_images.py" search \
   --query "company logo example" \
   --output-dir .dokkit/images/
 ```

package/optional-skills/dokkit/INGESTION.md

@@ -12,11 +12,11 @@ Parsing strategies and format routing for converting source documents into the d
 | HTML | Docling | `python -m docling <file> --to md` |
 | CSV | Docling | `python -m docling <file> --to md` |
 | MD | Direct copy | Read and process as-is |
-| XLSX | Custom | `python .claude/skills/dokkit/scripts/parse_xlsx.py` |
-| HWPX | Custom | `python .claude/skills/dokkit/scripts/parse_hwpx.py` |
+| XLSX | Custom | `python "$DEVLYN_SKILL_DIR/scripts/parse_xlsx.py"` |
+| HWPX | Custom | `python "$DEVLYN_SKILL_DIR/scripts/parse_hwpx.py"` |
 | JSON | Custom | Read, format as structured markdown |
 | TXT | Custom | Read, wrap as markdown |
-| PNG/JPG | Gemini Vision | `python .claude/skills/dokkit/scripts/parse_image_with_gemini.py` |
+| PNG/JPG | Gemini Vision | `python "$DEVLYN_SKILL_DIR/scripts/parse_image_with_gemini.py"` |
 
 ## Docling Usage
 

package/optional-skills/dokkit/PIPELINE.md

@@ -1,7 +1,8 @@
 # Dokkit Pipeline Reference
 
 Detailed step-by-step procedure for the one-command document filling pipeline.
-Auto-loaded when `/dokkit` is invoked.
+Read by the invoking skill before execution; bundled paths use the
+DEVLYN_SKILL_DIR binding it passes.
 
 ## Table of Contents
 
@@ -119,7 +120,7 @@ Report: `Phase 3/6: Generated content for N fields`
 Run the python-docx assembly script (NOT raw XML surgery):
 
 ```bash
-python .claude/skills/dokkit/scripts/fill_docx.py \
+python "$DEVLYN_SKILL_DIR/scripts/fill_docx.py" \
   <template.docx> \
   .dokkit/analysis.json \
   .dokkit/fill_content.json \
@@ -150,7 +151,7 @@ For each image field and image opportunity in `analysis.json`, run in parallel.
 **CRITICAL: Always pass `--field-id` and `--purpose`** so the image manifest tracks which image was generated for which slot. Without this, images get randomly assigned to the wrong slots.
 
 ```bash
-python .claude/skills/dokkit/scripts/source_images.py generate \
+python "$DEVLYN_SKILL_DIR/scripts/source_images.py" generate \
   --prompt "<prompt>" \
   --preset <preset> \
   --output-dir .dokkit/images/ \
@@ -345,4 +346,4 @@ Phase 5 → quality_gates results, iterations_count
 Phase 6 → exports[] entry added
 ```
 
-Validate after every write: `python ${CLAUDE_SKILL_DIR}/scripts/validate_state.py .dokkit/state.json`
+Validate after every write: `python "$DEVLYN_SKILL_DIR/scripts/validate_state.py" .dokkit/state.json`