feat(kyberforge): execute plugin-to-apm marketplace conversion

Why:
ADR-0015 established that Microsoft APM (apm.yml + .apm/) should replace
this repo's hand-authored plugin.json/marketplace.json model, with those
files becoming compiled output of `apm pack` instead of files edited by
hand via the (now-retired) plugin-author/marketplace-author skills.
Issue #90 was the deferred execution of that decision, gated on #88
(apm tooling) and #89 (apm-native agent-author/skill-author routing).

Implementation notes:
- All six plugins (bin, core, git, gitea, kyberforge, lint) now carry
  apm.yml + .apm/{skills,agents,hooks} as their authoring source. Skills
  moved with a plain git mv (content-identical across targets). Agents
  were re-authored, not moved: per ADR-0016, .apm/agents/*.agent.md
  compiles verbatim to both Claude and Copilot, so plugin-scope agents
  now carry only name/description/model/source_keys -- no tools: field,
  no Claude-only knobs (isolation, maxTurns, effort, memory,
  permissionMode).
- Root apm.yml registers all 7 marketplace packages (6 local plus
  mattpocock-skills as a remote entry) under versioning: per_package,
  matching this repo's existing independent-plugin-versioning practice.
- .claude-plugin/marketplace.json and every plugin's plugin.json are now
  apm-pack-compiled output, verified against the prior hand-maintained
  content: same names/descriptions/versions/licenses/authors, only
  cosmetic serialization differences (JSON key order, owner email vs.
  url, Unicode escaping).
- plugin-author and marketplace-author are retired now that apm-based
  authoring fully replaces their job; kyberforge bumped 1.3.1 -> 1.4.0
  for that removal, and the root marketplace catalog bumped
  0.3.1 -> 0.3.2 to match, per the version-bump convention now
  documented in apm-workflow's reference docs instead of a dedicated
  script (apm has no native version-bump automation).
- Fixed hardcoded pre-.apm/ path assumptions across
  .pre-commit-config.yaml, .pre-commit-hooks.yaml,
  scripts/check-scope-walkup-sync.sh, scripts/sync-vale-styles.sh,
  scripts/check-vale-style-sync.sh, six plugins' root plugin.json
  (stale skills/hooks/agents pointer fields that check-manifests.sh
  validates), and several tests/*.bats and tests/*.sh fixtures --
  including a bats REPO_ROOT relative-path depth bug (10 files, one
  extra .apm/ directory level to walk up) and a vale probe-path
  isolation regression introduced mid-fix.
- Corrected empirically-wrong assumptions surfaced this session in
  apm-workflow/apm-install's own reference docs: `apm marketplace
  package add` does not accept local paths (only owner/repo remote
  shorthand -- local packages are registered by editing apm.yml's
  marketplace.packages[] directly); `apm compile` is a consumer-side
  AGENTS.md/CLAUDE.md generator, not the plugin.json producer, and
  hard-fails on skill/agent-only packages without --clean; `apm plugin
  init <name>` nests a stray subdirectory when run with a positional
  name arg from inside a same-named directory; no native Copilot
  marketplace output profile exists; .mcp.json is merged into the
  compiled plugin.json content-aware and target-scoped, with no
  dependencies.mcp entry needed for simple passthrough; pipx is the
  correct pip fallback on externally-managed Python environments.
- Renamed agent-author's copilot.agent.md template asset to
  copilot.agent.md.template so apm compile's recursive *.agent.md glob
  stops misparsing the placeholder template as a real agent primitive.

Impact:
plugin.json and marketplace.json are compiled artifacts from here on --
editing them by hand is no longer the workflow; edit apm.yml/.apm/ and
run apm pack. CONTEXT.md's Plugin/Plugin marketplace glossary entries
reflect this. ADR-0001 is marked superseded, ADR-0006 moot, and
ADR-0010 updated for the new .apm/agents/ path (project/user scope
unaffected, per ADR-0016). Full local verification: claude plugin
validate --strict on all 6 plugins, apm audit --ci, apm marketplace
check, check-manifests.sh, and the full test suite (165/165 bats,
13/13 shell scripts) all pass clean.

Fixes: #90
Refs: #88, #89
ADR: 0015
ADR: 0016

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ub96PyaSRD9BHPktotj1pC

plugins/kyberforge/.apm/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/.apm/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/.apm/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/.apm/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/.apm/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/.apm/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.

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

@@ -0,0 +1,33 @@
+# tests/
+
+Test files for scripts bundled with this skill.
+
+## When to add tests
+
+Add tests here when the skill has scripts in `scripts/` that are complex enough
+to break silently — validators, parsers, generators, anything with branching
+logic or edge cases. Test infrastructure (`.bats`, `*_test.*`, `test_*.sh`)
+belongs here, not in `scripts/`.
+
+## Dependencies
+
+Tests require [bats-support](https://github.com/bats-core/bats-support) and
+[bats-assert](https://github.com/bats-core/bats-assert). The test files load
+helpers from the repo root's `tests/test_helper/`.
+
+From the repo root:
+
+```bash
+git clone https://github.com/bats-core/bats-support tests/test_helper/bats-support
+git clone https://github.com/bats-core/bats-assert tests/test_helper/bats-assert
+```
+
+Run all tests for this skill (from the repo root):
+
+```bash
+bats <destination-dir>/SKILL_NAME/tests/
+```
+
+## If no tests are needed
+
+Delete this README and the `tests/` directory entirely.