fix(kyberforge): address independent review of #154

Quote the template description so the raw scaffold is valid YAML, reject
newline-containing names in new-instructions.sh, correct the empty-compile
facts (exit 1, --clean exits 0), and finish removing commit steps from the
skill-author, agent-author and forge references. Adds regression tests.

Refs #148

Co-Authored-By: Claude Code <[email protected]>
Claude-Session: https://claude.ai/code/session_01KkT7RSDwDbmrM9T34b6sTi

plugins/kyberforge/.apm/skills/forge/references/author-routes.md

@@ -35,7 +35,7 @@ Fall back to an **inline invocation** — same conversation, no subagent — whe
 
 ## Two-tier verification
 
-Both author skills already close out with their own inline audit, in the same context as the
+The skill and agent author skills already close out with their own inline audit, in the same context as the
 authoring work: `skill-author` and `agent-author` each invoke `factory-audit` on what they wrote.
 That is tier one, and forge does not change it.
 

plugins/kyberforge/.apm/skills/forge/references/version-bump.md

@@ -31,7 +31,7 @@ brief:
 > "The package at `<package-path>` gained a new `<artifact-type>` (`<artifact-name>`). Bump the
 > `version` field in that package's `apm.yml`. Determine whether to bump minor (0.1.0) or patch
 > (0.0.1) based on whether this is a new capability (minor) or a fix/refactor (patch). Do not
-> release or tag — just update `apm.yml` and commit."
+> release or tag — just update `apm.yml`."
 
 Clean context rather than a fork is the point: the bump decision is made independently, without
 anchoring on the authoring conversation that just argued for the artifact's significance.