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/skills/skill-author/assets/templates/SKILL.md

@@ -1,105 +0,0 @@
----
-# 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.