Defame1297
5e232503c4
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
99 lines
3.4 KiB
Markdown
99 lines
3.4 KiB
Markdown
---
|
|
topic: milestones
|
|
source_keys:
|
|
- gitea-mcp-repo
|
|
- gitea-mcp-slim-go
|
|
---
|
|
|
|
# Milestone operations
|
|
|
|
Execution detail for `milestone_read` and `milestone_write`. Milestones are always repo-scoped —
|
|
there is no org-level milestone concept, unlike labels.
|
|
|
|
## Verified live schemas
|
|
|
|
`milestone_read` — required: `method`, `owner`, `repo`.
|
|
|
|
| Param | Type | Notes |
|
|
|---|---|---|
|
|
| `method` | string (enum) | `"get"` \| `"list"` |
|
|
| `owner` | string | required |
|
|
| `repo` | string | required |
|
|
| `id` | number | milestone ID, required for `"get"` |
|
|
| `name` | string | title filter, for `"list"` |
|
|
| `state` | string | default `"all"` — conventional values `"open"`/`"closed"`/`"all"`, but **not enforced by an enum in the live schema** (plain string). Any other value is passed through to Gitea rather than rejected client-side. |
|
|
| `page` | number | default `1` |
|
|
| `per_page` | number | default `30` |
|
|
|
|
`milestone_write` — required: `method`, `owner`, `repo`.
|
|
|
|
| Param | Type | Notes |
|
|
|---|---|---|
|
|
| `method` | string (enum) | `"create"` \| `"update"` \| `"edit"` \| `"delete"` — `"update"`/`"edit"` are aliases for the same operation; prefer `"update"` |
|
|
| `owner` | string | required |
|
|
| `repo` | string | required |
|
|
| `id` | number | required for update/delete |
|
|
| `title` | string | required for create |
|
|
| `description` | string | optional |
|
|
| `due_on` | string | due date — the live tool schema only describes this as an opaque "due date" string with no enforced format; ISO 8601 (e.g. `"2025-03-01T00:00:00Z"`) is the conventional value Gitea's REST API accepts, not something confirmed by the live MCP schema itself |
|
|
| `state` | string (enum) | `"open"` \| `"closed"` — **this one is schema-enforced**, unlike `milestone_read`'s `state` |
|
|
|
|
Note: unlike `label_read`/`label_write`, both milestone tools hard-require `owner` and `repo` at the
|
|
schema level — there's no scope variant to omit them for.
|
|
|
|
## List milestones
|
|
|
|
```
|
|
milestone_read method: "list" owner: <owner> repo: <repo> state: "open"
|
|
```
|
|
|
|
Report each as: id, title, state, due date, open/closed issue counts.
|
|
|
|
## Get one milestone
|
|
|
|
```
|
|
milestone_read method: "get" owner: <owner> repo: <repo> id: <id>
|
|
```
|
|
|
|
## Resolve a milestone ID from a title
|
|
|
|
Needed whenever the only handle available is a title — e.g. a `pull_request_read` response, which
|
|
returns `milestone` as a bare title string rather than `{id, title}`. Call:
|
|
|
|
```
|
|
milestone_read method: "list" owner: <owner> repo: <repo> name: <title>
|
|
```
|
|
|
|
and take the `id` of the matching result. If `name` filtering returns no match (e.g. due to a
|
|
title typo or case mismatch), fall back to listing without the filter and matching manually.
|
|
|
|
## Create a milestone
|
|
|
|
```
|
|
milestone_write method: "create"
|
|
owner: <owner> repo: <repo>
|
|
title: "v1.0"
|
|
description: "First stable release"
|
|
due_on: "2025-03-01T00:00:00Z"
|
|
```
|
|
|
|
Report the returned ID — the caller (`gitea-issues`/`gitea-prs`) needs it to assign issues/PRs to
|
|
this milestone via `issue_write`/`pull_request_write`.
|
|
|
|
## Update or close a milestone
|
|
|
|
```
|
|
milestone_write method: "update" owner: <owner> repo: <repo> id: <id> state: "closed"
|
|
```
|
|
|
|
Only pass the fields being changed — `id` plus any of `title`/`description`/`due_on`/`state`.
|
|
|
|
## Delete a milestone
|
|
|
|
```
|
|
milestone_write method: "delete" owner: <owner> repo: <repo> id: <id>
|
|
```
|
|
|
|
Deleting a milestone does not delete or unassign the issues/PRs that referenced it — they simply
|
|
lose the milestone reference.
|