fix(kyberforge): bridge apm content to Claude Code's flat plugin discovery

Claude Code's (and Copilot's) native plugin installer has zero awareness of
.apm/ nesting -- it convention-scans only flat skills/, agents/, commands/,
hooks.json at each plugin's root. Confirmed via strings on the installed
claude binary and live installs of git@holocron/gitea@holocron/kyberforge@
holocron, all reporting Skills(0) Agents(0) Hooks(0) post ADR-0015's apm
conversion. Root cause (apm_cli/core/plugin_manifest.py): apm's plugin.json
compiler deliberately strips skills/agents/commands keys, assuming the host
already auto-discovers those convention directories -- it has no model of
.apm/ being host-visible at all. Separately, apm's own bundle exporter
(apm_cli/bundle/plugin_exporter.py, behind `apm pack --format plugin`)
implements the correct .apm/ -> flat mapping, but only ever targeted
build/<name>-<version>/, a path nothing in marketplace.json's source: points
at.

scripts/sync-plugin-content.sh wraps that bundle exporter and copies its
agents/, skills/, commands/, instructions/, extensions/, and merged
hooks.json back into each plugin's own root as a second tracked
compiled-output category -- same governance status as
.claude-plugin/plugin.json: generated from .apm/, never hand-edited. tests/
subdirectories are excluded from the mirror (dev fixtures, not host-visible
runtime content; several hardcode a relative repo-root walk-up sized for the
.apm/-nested depth, which breaks when duplicated one level shallower).
Applied for real across all 6 plugins and verified two ways: `claude plugin
validate --strict` passes on every real plugin directory, and a live
`claude --plugin-dir <path> -p "list skills/agents"` behavioral test
confirms content is now actually discovered.

Also, from the same issue #90 review round:
- scripts/check-manifests.sh pointed at each plugin's root-level plugin.json
  (checking skills/hooks/mcpServers/agents pointer fields) -- that file was a
  stale near-duplicate of .claude-plugin/plugin.json nothing else read or
  wrote, now deleted across all 6 plugins. check-manifests.sh is rewritten to
  validate .claude-plugin/plugin.json instead, and drops the pointer-field
  checks entirely (nothing to check -- those fields are correctly absent by
  design). Content-presence drift is now check-plugin-content-sync's job, a
  new pre-push hook wired in .pre-commit-config.yaml.

docs/adr/0017 records the root cause and decision in full, including two
rejected alternatives (patching plugin.json's path fields directly -- apm's
compiler strips them on every run; pointing marketplace.json at apm pack's
build/ output -- a version-suffixed non-source directory nothing can install
from without an extra build step). ADR-0015 and CONTEXT.md are updated to
point at it.

Refs: #90

plugins/kyberforge/skills/skill-author/assets/templates/README.md

@@ -0,0 +1,51 @@
+# SKILL_NAME
+
+<!-- FILL IN: One sentence describing what this skill does. -->
+
+## What it does
+
+<!-- FILL IN: 2–4 sentences. What task does this skill handle?
+     What does the agent produce or accomplish when it runs? -->
+
+## Before you start
+
+<!-- FILL IN: List any prerequisites the user should have ready.
+     Examples: research docs, a grill session, specific input files, credentials.
+     Delete this section if the skill has no meaningful prerequisites. -->
+
+## Usage
+
+```
+/SKILL_NAME
+```
+
+<!-- FILL IN: Add any required or common arguments.
+     If the skill takes no arguments, delete the code block above and just keep the slash command. -->
+
+<!-- OPTIONAL: Manual (human) workflow — include if the skill bundles scripts a human can run directly.
+
+**Manual workflow:**
+```bash
+# FILL IN: step-by-step commands
+```
+-->
+
+## Files
+
+<!-- FILL IN: List each file individually. Remove rows for directories you deleted.
+     Replace the example rows below with your actual files. -->
+
+| File | Purpose |
+|------|---------|
+| `SKILL.md` | Skill instructions for agents |
+| `scripts/your-script.sh` | FILL IN: what this script does |
+| `references/your-doc.md` | FILL IN: what this reference covers |
+| `assets/your-asset.json` | FILL IN: what this asset is |
+| `tests/your-test.bats` | FILL IN: what this test covers |
+
+<!-- OPTIONAL: Spec reference — include if this skill implements or follows an external standard.
+
+## Spec reference
+
+[FILL IN: Spec name](FILL IN: URL)
+-->

plugins/kyberforge/skills/skill-author/assets/templates/SKILL.md

@@ -0,0 +1,105 @@
+---
+# SKILL.md — agentskills.io skill definition
+# Fill in all FILL IN: placeholders. Remove comment blocks that don't apply.
+
+name: SKILL_NAME
+# Required. Must exactly match the parent directory name.
+# Valid characters: lowercase letters, numbers, hyphens.
+# Invalid: uppercase, leading/trailing/consecutive hyphens.
+# Max length: 64 characters.
+# Examples: my-tool, data-analyzer, pdf-processor
+
+description: >
+  FILL IN: What does this skill do? State capabilities specifically
+  (e.g. "parses and validates OpenAPI specs", not "helps with APIs").
+  Use when FILL IN: when should an agent activate this skill?
+  Include indirect triggers: even if the user doesn't mention X explicitly.
+  Do not use when FILL IN: near-miss exclusions — remove this line if none apply.
+
+# license: MIT
+# Optional. License name (e.g. MIT, Apache-2.0) or relative path to a bundled
+# license file. Include when distributing this skill. Omit for private/internal use.
+
+# compatibility: Requires python3 >= 3.10 and uv
+# Optional. 1–500 characters. State tool requirements, runtime versions,
+# and network access needs. Omit for skills with no special environment requirements.
+
+# metadata:
+#   author: your-name
+#   version: "1.0"
+#   category: general
+#   source_keys:
+#     - source-slug-one
+#     - source-slug-two
+# Optional. Arbitrary key-value map. Common keys: author, version, category.
+# source_keys: populated when built from /research output. Lists slugs from references/sources.md.
+# Also add source_keys to each references/*.md file that was informed by research.
+
+# allowed-tools: Bash Read Write
+# Optional (experimental — support varies by client).
+# Space-separated list of pre-approved tools.
+# Use when tool usage is known and bounded, to reduce permission prompts.
+---
+
+<!-- ============================================================
+  SKILL BODY
+
+  Include only what the agent lacks:
+    - Domain conventions the agent cannot infer from general knowledge
+    - Non-obvious sequences or ordering constraints
+    - One default per decision point + one escape hatch (never a menu)
+    - Gotchas — facts that defy reasonable assumptions
+
+  Omit:
+    - Concepts the agent already knows
+    - Exhaustive option lists
+    - Steps the agent handles independently
+    - Restatements of the description
+
+  Size budget: under 500 lines / 5000 tokens.
+  Move reference material to references/ and load it conditionally.
+  Bundle repeated executable logic into scripts/.
+
+  Delete this comment block before shipping.
+============================================================ -->
+
+<!-- OPTIONAL: Gotchas section — highest-value content. Place near the top.
+     Add facts that defy reasonable assumptions or non-obvious constraints.
+
+## Gotchas
+
+- FILL IN: fact that defies a reasonable assumption
+- FILL IN: non-obvious naming discrepancy or hidden constraint
+-->
+
+<!-- OPTIONAL: Multi-step workflow checklist.
+
+## Workflow
+
+- [ ] Step 1: FILL IN
+- [ ] Step 2: FILL IN
+- [ ] Step 3: FILL IN
+-->
+
+<!-- OPTIONAL: Output format template — use when the agent must produce a specific format.
+
+## Output format
+
+Use this structure:
+
+```markdown
+# [FILL IN: Title]
+
+## FILL IN: Section
+FILL IN: what goes here
+```
+-->
+
+<!-- OPTIONAL: Conditional reference — load documentation only when needed.
+
+If FILL IN: condition, read `references/FILL IN: filename.md`.
+-->
+
+## FILL IN: <section-name (e.g. Step 1, Workflow, Instructions)>
+
+FILL IN: Add your skill instructions here. Replace this section header and body with your skill content.

plugins/kyberforge/skills/skill-author/assets/templates/assets/README.md

@@ -0,0 +1,29 @@
+# assets/
+
+Static resources bundled with this skill: templates, schemas, lookup tables,
+sample data, images.
+
+## When to add an asset
+
+Add a file here when the skill needs a static resource that:
+- Would be tedious to reproduce in instructions (a full JSON schema, a CSV
+  lookup table, a binary template)
+- Needs to be referenced by path rather than inlined in SKILL.md
+
+## How to reference from SKILL.md
+
+Use a relative path from the skill root:
+
+```markdown
+Use the schema at `assets/response-schema.json` to validate output.
+```
+
+Or instruct the agent to load it conditionally:
+
+```markdown
+If validating output format, use `assets/response-schema.json`.
+```
+
+## If no assets are needed
+
+Delete this README and the `assets/` directory entirely.

plugins/kyberforge/skills/skill-author/assets/templates/references/README.md

@@ -0,0 +1,31 @@
+# references/
+
+Additional documentation agents load on demand. Files here extend SKILL.md
+without bloating its core context.
+
+## When to add a reference file
+
+Move content here when SKILL.md is approaching 500 lines, or when a topic
+is only relevant in specific circumstances (error handling, edge cases,
+domain-specific sub-procedures).
+
+## How to reference from SKILL.md
+
+Load conditionally — tell the agent exactly when to read each file:
+
+```markdown
+If the API returns a non-200 status, read `references/api-errors.md`.
+```
+
+Avoid generic "see references/ for details" — the agent loads context on
+demand, so give it a precise trigger condition.
+
+## File conventions
+
+- One topic per file — focused files mean less unnecessary context loaded
+- Kebab-case filenames (e.g. `api-errors.md`, `output-formats.md`)
+- Keep files under 200 lines where possible
+
+## If no reference files are needed
+
+Delete this README and the `references/` directory entirely.

plugins/kyberforge/skills/skill-author/assets/templates/references/sources.md

@@ -0,0 +1,14 @@
+# Sources
+
+<!-- Populated at Step 5 of skill authoring, after all skill files are written.
+     For each research source with status `extracted`, record which skill files
+     it contributed to under Contributing files.
+     Delete this file if no research sources were provided as input. -->
+
+## FILL IN: source-slug
+
+- **URL:** FILL IN
+- **Description:** FILL IN
+- **Research doc:** FILL IN: path to the plugin-level research sources file this entry came from (e.g. plugins/myplugin/docs/research/docs/<topic>/sources.md), relative to repo root
+- **Contributing files:** FILL IN: comma-separated list of skill files this source informed (e.g. SKILL.md, references/foo.md). Use `(none)` if the source was consulted but contributed no file content directly.
+- **Status:** `extracted`

plugins/kyberforge/skills/skill-author/assets/templates/scripts/README.md

@@ -0,0 +1,47 @@
+# scripts/
+
+Executable code bundled with this skill. Agents run scripts in this directory
+to perform repeatable operations rather than reinventing the logic each run.
+
+## When to add a script
+
+Add a script when agents independently reinvent the same logic across runs —
+building the same parser, chart, or validation routine from scratch each time.
+Bundle it here once, tested and reliable.
+
+## Script requirements (agentskills.io)
+
+Scripts must be designed for non-interactive, agentic execution:
+
+- **No interactive prompts** — agents run in non-interactive shells.
+  Accept all input via flags, env vars, or stdin. A script that blocks on
+  TTY input hangs indefinitely.
+- **Expose `--help`** — this is how agents learn your script's interface.
+  Keep the output concise; it enters the agent's context window.
+- **Structured output** — write data (JSON, CSV, TSV) to stdout.
+  Write progress, warnings, and diagnostics to stderr.
+- **Idempotent** — prefer "create if not exists" over "create and fail on
+  duplicate". Agents may retry on failure.
+- **Meaningful exit codes** — `0` for success, non-zero for failure.
+  Use distinct codes for different failure types; document them in `--help`.
+- **Dry-run support** — add `--dry-run` for destructive operations.
+
+## Self-contained scripts
+
+Bundle dependencies inline so the agent can run the script with a single command.
+
+Python (PEP 723 + uv):
+```python
+# /// script
+# dependencies = ["requests>=2.31,<3"]
+# requires-python = ">=3.11"
+# ///
+import requests
+```
+```bash
+uv run scripts/my-script.py
+```
+
+## If no scripts are needed
+
+Delete this README and the `scripts/` directory entirely.