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/core/skills/agentsmd-author/references/content-guide.md

@@ -1,118 +0,0 @@
----
-source_keys:
-  - agents-md-official
-  - context7-websites-agents-md
-  - context7-agentsmd-agents-md
----
-
-# What good AGENTS.md content looks like
-
-AGENTS.md has no required schema — there's no field to fill in, only sections that either
-earn their place or don't. Agents treat this file as a set of live directives, not
-documentation: they will actually run the commands it lists and fix failures before
-finishing a task. That means a wrong or stale line is worse than a missing one. Verify
-every command against something real in the repo before writing it down.
-
-## Section-by-section guidance
-
-**Setup / build commands** — the install and dev-server commands, exactly as they appear
-in `package.json` scripts, a `Makefile`, or a `Cargo.toml`/`pyproject.toml` equivalent. One
-line per command, each with a one-clause note on what it does if the name alone isn't
-obvious. Skip this section if there's genuinely nothing beyond "clone and run" — don't pad
-it with a restated `git clone`.
-
-**Code style** — only conventions that aren't already enforced by a linter/formatter config
-the agent will pick up on its own (a `.eslintrc`, `rustfmt.toml`, etc. speaks for itself).
-Write down the conventions that live only in people's heads: naming patterns, module
-boundaries, patterns to avoid, anything a linter can't catch. If the repo has no
-undocumented conventions beyond what tooling enforces, skip this section.
-
-**Testing instructions** — the exact command(s) to run the suite, where to find
-per-package or per-workflow test configuration (e.g. `.github/workflows/`), and any
-non-obvious requirement (a service that must be running, an env var that must be set).
-State plainly that the agent should run tests before considering a change done and fix
-failures — don't leave this implicit.
-
-**Security considerations** — only repo-specific hazards: a data-handling boundary, a
-credential pattern to never hardcode, a destructive command that needs a confirmation
-step. Do not restate general security advice ("don't commit secrets") that any agent
-already assumes — that's padding, not a directive.
-
-**Commit / PR conventions** — the title/format convention if one exists (e.g. a
-Conventional Commits type prefix, a ticket-number requirement), and any check that must
-pass before a PR is opened (lint, test, type-check). Point at the real command, not
-"make sure it passes."
-
-**Dev environment tips** — the handful of things that save real time and are easy to miss:
-how to jump to a specific package in a monorepo without `ls`-ing around, how to register a
-new package so the toolchain sees it, where to look up a canonical name/id. This section
-is for genuine friction points observed in this repo, not generic advice.
-
-## What separates useful content from padding
-
-A useful section names a real file, command, or path that exists in this repo right now.
-A padded section could be pasted into any repo unchanged and still "make sense" — that's
-the tell. If a sentence would read the same in a different codebase, it doesn't belong.
-Prefer four accurate lines over twelve generic ones.
-
-## Worked example (minimal project)
-
-```markdown
-# AGENTS.md
-
-## Setup commands
-- Install deps: `pnpm install`
-- Start dev server: `pnpm dev`
-- Run tests: `pnpm test`
-
-## Code style
-- TypeScript strict mode
-- Single quotes, no semicolons
-- Use functional patterns where possible
-
-## Dev environment tips
-- Use `pnpm dlx turbo run where <project_name>` to jump to a package instead of scanning with `ls`.
-- Run `pnpm install --filter <project_name>` to add the package to your workspace so Vite, ESLint, and TypeScript can see it.
-- Check the `name` field inside each package's `package.json` to confirm the right name.
-
-## Testing instructions
-- Find the CI plan in the `.github/workflows` folder.
-- Run `pnpm turbo run test --filter <project_name>` to run every check defined for that package.
-- From the package root you can just call `pnpm test`. The commit should pass all tests before you merge.
-- Fix any test or type errors until the whole suite is green.
-- Add or update tests for the code you change, even if nobody asked.
-
-## PR instructions
-- Title format: [<project_name>] <Title>
-- Always run `pnpm lint` and `pnpm test` before committing.
-```
-
-Every line above names a real command or path — that's the standard to hold this repo's
-version to, not the specific tooling shown (a Python/Cargo/Go repo's AGENTS.md should look
-nothing like this one in its specifics, only in how concrete each line is).
-
-## Monorepo / nested placement
-
-```
-my-monorepo/
-├── AGENTS.md              # Root-level: applies to the whole repo
-├── packages/
-│   ├── api/
-│   │   └── AGENTS.md      # API-specific instructions; overrides root for this package
-│   ├── web/
-│   │   └── AGENTS.md      # Web app-specific instructions
-│   └── shared/
-│       └── AGENTS.md      # Shared library instructions
-```
-
-Precedence rule: the file nearest the edited path wins. Nested files are **not** merged
-with the root file — an agent editing inside `packages/api/` reads only
-`packages/api/AGENTS.md`, never the root file in addition. Consequences:
-
-- A nested file must stand alone. Don't write "also see the root file" — write what the
-  agent needs, full stop.
-- Don't duplicate root content in a nested file "just in case." If a nested file repeats
-  root-level setup instructions verbatim, that's a sign it shouldn't exist as a separate
-  file at all — the subtree isn't actually different enough to warrant one.
-- Only create a nested file when the subtree has a genuinely different stack, build tool,
-  or convention than the root (see `SKILL.md` Step 2 for the placement decision itself).

plugins/core/skills/agentsmd-author/references/sources.md

@@ -1,25 +0,0 @@
-# Sources
-
-## agents-md-official
-
-- **URL:** https://agents.md/
-- **Description:** Official agents.md website — format spec, common-sections checklist, precedence rules (nearest-file-wins, no merge across files), monorepo nesting patterns
-- **Research doc:** plugins/core/docs/research/docs/agentsmd/sources.md
-- **Contributing files:** SKILL.md, references/content-guide.md
-- **Status:** `extracted`
-
-## context7-websites-agents-md
-
-- **URL:** context7:/websites/agents_md
-- **Description:** Context7 index of the official agents.md website — overview, governance, cross-tool compatibility, configuration examples
-- **Research doc:** plugins/core/docs/research/docs/agentsmd/sources.md
-- **Contributing files:** SKILL.md, references/content-guide.md
-- **Status:** `extracted`
-
-## context7-agentsmd-agents-md
-
-- **URL:** context7:/agentsmd/agents.md
-- **Description:** Context7 index of the agentsmd/agents.md repository — format spec, nested monorepo patterns, file structure examples
-- **Research doc:** plugins/core/docs/research/docs/agentsmd/sources.md
-- **Contributing files:** SKILL.md, references/content-guide.md
-- **Status:** `extracted`