-
Gitea user account used by Claude Code with Gitea MCP to manage repositories: read/write issues and PRs, comment on changes, and perform merge/review actions with appropriate permissions.
- Joined on
2026-06-20
This Hard Rule governs 'any apm.yml content this orchestrator writes or edits', but the agent declares only tools: Bash, Read (line 6) and its own Scope (line 13) states it 'does not decide manifest content yourself, you delegate' — it has no Edit/Write tool and never touches apm.yml directly. The rule it exists to enforce has no code path that ever fires; it reads as an active safety gate but is dead text. Either grant the capability this rule assumes, or move the rule to wherever manifest content actually gets written.
The compile-manifest-check operation has no corresponding apm CLI command anywhere in apm-workflow's references or the shipped microsoft-apm research docs (verified by grep across both). An executing agent dispatched this operation has to invent behavior since nothing documents what to actually run.
add-package and add-marketplace are never mapped to their underlying apm marketplace package add / apm marketplace add commands anywhere in this file, despite this same file's Hard Rule insisting these two directions must 'never guess from context alone.' An executing agent has no explicit mapping table and could plausibly invert them — exactly the mix-up the adjacent rule was written to prevent.
apm-orchestrate.md and apm-orchestrate.agent.md duplicate ~95% of their content verbatim and have already drifted on the Output section: the .md version gives an explicit JSON schema with enumerated error codes (not_confirmed
Documents a raw git add/git commit/git tag/git push --tags chain as the literal release step. AGENTS.md's 'Prefer plugin skills over raw shell' section states commits/remotes are owned by git:git-commits/git:git-remotes and to fall back to raw shell 'only when no skill covers it' — an agent following this reference verbatim shells out directly in a repo that already has dedicated skills for exactly this operation.
This and the other three apm-workflow reference files (compile.md, audit.md, marketplace.md) restate their sibling research docs under docs/research/docs/microsoft-apm/ nearly verbatim (same command lists, same caveats, same CI YAML block in audit.md) — two sources of truth for the same facts. An upstream apm flag/behavior change applied to the research doc (the stated source of truth) can be missed here, leaving the actionable skill guidance silently stale while looking equally authoritative. Consider having these reference files point at the research docs rather than duplicating their content.
This Decision bullet states 'This directly supersedes ADR-0001' as a present-tense fact, but the Consequences section (line 63) says 'ADR-0001 is superseded once issue #90 executes' — a future, conditional event. The same document licenses opposite conclusions depending which section a reader lands on. Pick one framing (recommend: conditional, matching Consequences) and make the Decision bullet match it.
Decision record: ADR-0015 (docs/adr/0015-apm-replaces-plugin-marketplace-authoring.md, commit 0e421ac on feat/88-marketplace-apm-conversion) — replaces the plugin/marketplace authoring model…
PR #85 merged to main at 8f523da. Tagged and released v1.0.0 from that commit: https://git.dev.rkdr.net/Defame1297/holocron/releases/tag/v1.0.0
External consumers can now pin `.pre-commit-ho…
Follow-up — cf5de2b, plus PR description corrected
cf5de2b — the third finding from my last pass, previously left as low-severity/optional: check-vale-style-sync.sh silently exited…
Independent review + fixes — 389a4f0 → 76e0df6
Ran three parallel review passes against the branch as it stood at e62f68a (verification of round-2's blocking items/gaps against the…
Pre-merge review (round 4)
Ran four parallel review passes against the branch (verification gate, correctness/simplification/efficiency code review, security review, and a dogfooded `skill-audi…
Round 6 — review findings addressed (57654c4..9a3f72b)
A full review of the branch (commit history + final state) produced 12 findings; each was then cross-checked against this thread…