fix(kyberforge): resolve PR #144 review and audit round 1

- factory-audit: no-op hooks, ./ after interpreters, split-quote and
  spaced ${PLUGIN_ROOT} paths, camelCase events in Claude-targeted flat
  files, case-insensitive routing stems, and non-string YAML keys are
  now caught; input: forms and prompt boundary clauses align with
  primitive-author; bats 347 -> 367
- primitive-author: routing forms, quoting guidance, install exit on
  hidden Unicode, argument-hint exception
- forge: drop duplicated gotcha, fit description and body budgets (#143)
- skill-author: primitive-author boundary, Claude-only env vars
- hook: exit unless CLAUDE_PROJECT_DIR is set, so Copilot/Codex never
  run apm update; ADR-0019 correction, ADR-0025 amendment, docs fixes

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi

plugins/kyberforge/.apm/skills/forge/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: forge
 description: >
-  Use when the user wants to build or improve something but has not yet named
-  the artifact type; "not sure if this should be a skill or a plugin", "I have
-  an idea but don't know where it belongs". Routes to the matching author
-  skill. Do not use when the type is already named — invoke `skill-author`,
-  `agent-author`, `primitive-author` or `apm-workflow` directly.
+  Use when the user wants to build or improve something but has not named its
+  type ("skill or plugin?"). Not a skill -> skill-author.
+  Not an agent -> agent-author.
+  Not a hook, instruction or prompt -> primitive-author.
+  Not a plugin -> apm-workflow.
 metadata:
   version: "1.0.2"
   category: factory
@@ -17,16 +17,15 @@ metadata:
 
 ## Gotchas
 
-- forge is an optional guided entry point, not a gate — `skill-author`, `agent-author`, `primitive-author`, `factory-audit` and `apm-workflow` all stay directly invokable, and forge never intercepts a direct call to one.
 - Claude Code's skill-level `context: fork` frontmatter field and the `/fork` subagent command are opposites despite the shared word: `context: fork` isolates (fresh context, no parent access), while `/fork` inherits the full conversation. The route reference each classification loads spends that distinction: `references/author-routes.md` chooses between the two, `references/apm-routes.md` rules the fork out.
 
 ## Step 1 — Grill the intent
 
 Call `grill-with-docs` unless a grill session has already run and is available in the context.
 
-`grill-with-docs` ships in a sibling plugin that kyberforge does not declare as an apm dependency, so it resolves in the authoring monorepo but can be absent where kyberforge is installed alone. If it does not resolve, grill inline yourself rather than skipping the step: what problem the artifact solves, who invokes it and how, what it must refuse, and which existing skill or plugin already owns part of the job. Say which path you took.
+If `grill-with-docs` does not resolve, read `references/grill-fallback.md`.
 
-Grilling regularly overturns the artifact type assumed at the start, or splits one idea into several artifacts, so it runs before classification rather than confirming it. Run it inline in the current conversation — grilling is interactive and a subagent cannot hold the back-and-forth.
+Grilling often overturns or splits the assumed type, so it runs before classification, inline — a subagent cannot hold the back-and-forth.
 
 ## Step 2 — Classify and dispatch