Defame1297
38f1ba4e03
Claude Code's (and Copilot's) native plugin installer has zero awareness of .apm/ nesting -- it convention-scans only flat skills/, agents/, commands/, hooks.json at each plugin's root. Confirmed via strings on the installed claude binary and live installs of git@holocron/gitea@holocron/kyberforge@ holocron, all reporting Skills(0) Agents(0) Hooks(0) post ADR-0015's apm conversion. Root cause (apm_cli/core/plugin_manifest.py): apm's plugin.json compiler deliberately strips skills/agents/commands keys, assuming the host already auto-discovers those convention directories -- it has no model of .apm/ being host-visible at all. Separately, apm's own bundle exporter (apm_cli/bundle/plugin_exporter.py, behind `apm pack --format plugin`) implements the correct .apm/ -> flat mapping, but only ever targeted build/<name>-<version>/, a path nothing in marketplace.json's source: points at. scripts/sync-plugin-content.sh wraps that bundle exporter and copies its agents/, skills/, commands/, instructions/, extensions/, and merged hooks.json back into each plugin's own root as a second tracked compiled-output category -- same governance status as .claude-plugin/plugin.json: generated from .apm/, never hand-edited. tests/ subdirectories are excluded from the mirror (dev fixtures, not host-visible runtime content; several hardcode a relative repo-root walk-up sized for the .apm/-nested depth, which breaks when duplicated one level shallower). Applied for real across all 6 plugins and verified two ways: `claude plugin validate --strict` passes on every real plugin directory, and a live `claude --plugin-dir <path> -p "list skills/agents"` behavioral test confirms content is now actually discovered. Also, from the same issue #90 review round: - scripts/check-manifests.sh pointed at each plugin's root-level plugin.json (checking skills/hooks/mcpServers/agents pointer fields) -- that file was a stale near-duplicate of .claude-plugin/plugin.json nothing else read or wrote, now deleted across all 6 plugins. check-manifests.sh is rewritten to validate .claude-plugin/plugin.json instead, and drops the pointer-field checks entirely (nothing to check -- those fields are correctly absent by design). Content-presence drift is now check-plugin-content-sync's job, a new pre-push hook wired in .pre-commit-config.yaml. docs/adr/0017 records the root cause and decision in full, including two rejected alternatives (patching plugin.json's path fields directly -- apm's compiler strips them on every run; pointing marketplace.json at apm pack's build/ output -- a version-suffixed non-source directory nothing can install from without an extra build step). ADR-0015 and CONTEXT.md are updated to point at it. Refs: #90
98 lines
3.3 KiB
Markdown
98 lines
3.3 KiB
Markdown
---
|
|
topic: labels
|
|
source_keys:
|
|
- gitea-mcp-repo
|
|
- gitea-mcp-slim-go
|
|
---
|
|
|
|
# Label operations
|
|
|
|
Execution detail for `label_read` and `label_write`. Both tools operate on either **repo-scoped**
|
|
or **org-scoped** labels — never both in one call. Pick the method family (`*_repo_label*` vs.
|
|
`*_org_label*`) that matches the target, and pass `owner`+`repo` or `org` accordingly.
|
|
|
|
## Verified live schemas
|
|
|
|
`label_read` — required: `method`.
|
|
|
|
| Param | Type | Notes |
|
|
|---|---|---|
|
|
| `method` | string (enum) | `"list_repo_labels"` \| `"get_repo_label"` \| `"list_org_labels"` |
|
|
| `owner` | string | for repo methods |
|
|
| `repo` | string | for repo methods |
|
|
| `org` | string | for org methods |
|
|
| `id` | number | label ID, required for `"get_repo_label"` |
|
|
| `page` | number | default `1` |
|
|
| `per_page` | number | default `30` |
|
|
|
|
`label_write` — required: `method`.
|
|
|
|
| Param | Type | Notes |
|
|
|---|---|---|
|
|
| `method` | string (enum) | `"create_repo_label"` \| `"edit_repo_label"` \| `"delete_repo_label"` \| `"create_org_label"` \| `"edit_org_label"` \| `"delete_org_label"` |
|
|
| `owner` | string | for repo methods |
|
|
| `repo` | string | for repo methods |
|
|
| `org` | string | for org methods |
|
|
| `id` | number | for edit/delete |
|
|
| `name` | string | required for create |
|
|
| `color` | string | hex `#RRGGBB`, required for create |
|
|
| `description` | string | optional |
|
|
| `exclusive` | boolean | org labels only |
|
|
| `is_archived` | boolean | repo labels only |
|
|
|
|
Note: unlike `milestone_read`/`milestone_write`, `owner`/`repo`/`org` are **not** schema-required on
|
|
either label tool — only `method` is. Passing none for a repo/org method still fails, just as a
|
|
runtime error from Gitea rather than a client-side validation error.
|
|
|
|
## List repo labels
|
|
|
|
```
|
|
label_read method: "list_repo_labels" owner: <owner> repo: <repo> per_page: 50
|
|
```
|
|
|
|
Paginate (`page: 1, 2, ...`) until the returned count is less than `per_page`. This is the only way
|
|
to build a complete name → ID map — there is no lookup-by-name endpoint.
|
|
|
|
## Get one label
|
|
|
|
```
|
|
label_read method: "get_repo_label" owner: <owner> repo: <repo> id: <id>
|
|
```
|
|
|
|
## Resolve a name to an ID
|
|
|
|
There is no direct name lookup. List all repo labels (paginating if needed), scan for a
|
|
case-insensitive name match, and extract `id`. This is the required first step before any label
|
|
application on an issue or PR — the actual `add_labels`/`replace_labels`/`remove_label` call lives
|
|
in `gitea-issues`/`gitea-prs` via `issue_write`/`pull_request_write`, which take numeric IDs only.
|
|
|
|
## Create a label
|
|
|
|
```
|
|
label_write method: "create_repo_label"
|
|
owner: <owner> repo: <repo>
|
|
name: "Kind/Bug"
|
|
color: "#d73a4a"
|
|
description: "Confirmed bug"
|
|
```
|
|
|
|
For an org label, use `method: "create_org_label"` with `org:` instead of `owner`/`repo`, and
|
|
`exclusive: true` if the label belongs to a mutually-exclusive scope group.
|
|
|
|
## Edit a label
|
|
|
|
```
|
|
label_write method: "edit_repo_label" owner: <owner> repo: <repo> id: <id> color: "#ff0000"
|
|
```
|
|
|
|
Only pass the fields being changed — `id` plus any of `name`/`color`/`description`/`is_archived`.
|
|
|
|
## Delete a label
|
|
|
|
```
|
|
label_write method: "delete_repo_label" owner: <owner> repo: <repo> id: <id>
|
|
```
|
|
|
|
Deleting a label does not remove it from historical issue/PR timeline events — it disappears only
|
|
from current label lists.
|