docs: OpenSpec change for label CRUD tools + label resource-templates #192
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/OpenSpec
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
RFC - Request For Comments
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
hermes-attempted
hermes-needs-clarification
hermes-ready
hermes-review
hermes-wip
human-required
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
agentic-forges/forgejo-mcp!192
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/192/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
OpenSpec change
label-crudfor Codeberg #190. Proposal + design + specs + tasks only — no implementation. Adversarially reviewed by a debate team (seedesign.md § Adversarial Review — 2026-06-02).Two new capabilities + one modified:
label-crud— 8 label toolsforgejo-sdk/v3):create_repo_label/edit_repo_label/delete_repo_label/get_repo_label.pkg/forgejoraw-HTTPDoJSONagainst/orgs/{org}/labels— no SDK method):create_org_label/edit_org_label/delete_org_label/get_org_label.rrggbb→#rrggbb, 6-digit only, invalid →-32602);edit_*is PATCH (only supplied fields change).delete_repo_label/delete_org_labeltakedelete_mode: "safe"|"force"(defaultsafe) + an in-use guard — count issues/PRs referencing the label, refuse and report the count unlessdelete_mode="force". Repo count via SDKListRepoIssuespagination (DoJSONcan't readX-Total-Count); org count iterates the org's repos, best-effort (MAY under-count repos the token can't read; the refusal says so).mcp-resource-label— 3forgejo://templatesforgejo://repo/{owner}/{repo}/labels{?page,limit}(client-controlled bound, sentinel →list_repo_labels)forgejo://repo/{owner}/{repo}/label/{id}(single)forgejo://org/{org}/labels{?page,limit}(org list, sentinel →list_org_labels)page/limitare the client-controlled bound;EmbeddedListCapis the safety ceiling. Scope-lessforgejo://label/{id}is invalid.403→-32002,404→-32003.mcp-resources-core(MODIFIED)Adds a Collection resource requirement —
forgejo://.../labelsis the first standalone collection-as-resource. Records the precedent normatively so future list entities cite the framework.Out of scope
exclusive/is_archivedfields — not modelled by SDK v3Label; reserved as forward-compatible optional params.Pre-code verification gates (in design Open Questions)
GET /orgs/{org}/labels/{id}exists in pinned Forgejo (elseget_org_label= list-and-filter).Dependency / ordering
The
mcp-resources-coredelta assumesmcp-resource-templatesarchived first (it owns the unarchived core capability).label-crudSHOULD archive after it.Validation
openspec validate label-crud --strict→ valid. Pre-commit clean.Note: repo tool names (
create_repo_label…) differ from #190's statedcreate_label… — renamed for org/repo symmetry; map on acceptance.Codeberg #190
op1st Pipelines as Code/forgejo-mcp-code-scans-9x6rt is running.
Starting Pipelinerun forgejo-mcp-code-scans-9x6rt in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-9x6rt -fop1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-99bqt is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-99bqt in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-99bqt -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-thwkz is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-thwkz in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-thwkz -fop1st Pipelines as Code/forgejo-mcp-code-scans-9x6rt has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-99bqt has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-thwkz has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-26mpm is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-26mpm in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-26mpm -fop1st Pipelines as Code/forgejo-mcp-code-scans-wmww4 is running.
Starting Pipelinerun forgejo-mcp-code-scans-wmww4 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-wmww4 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-lgfxs is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-lgfxs in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-lgfxs -fop1st Pipelines as Code/forgejo-mcp-code-scans-wmww4 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-26mpm has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-lgfxs has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-on-pull-request-zjw5k is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-zjw5k in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-zjw5k -fop1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-jgj65 is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-jgj65 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-jgj65 -fop1st Pipelines as Code/forgejo-mcp-code-scans-57q9n is running.
Starting Pipelinerun forgejo-mcp-code-scans-57q9n in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-57q9n -fop1st Pipelines as Code/forgejo-mcp-code-scans-57q9n has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-jgj65 has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-zjw5k has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-gc2zk is running.
Starting Pipelinerun forgejo-mcp-code-scans-gc2zk in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-gc2zk -fop1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-z6xc6 is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-z6xc6 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-z6xc6 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-jr85n is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-jr85n in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-jr85n -fop1st Pipelines as Code/forgejo-mcp-code-scans-gc2zk has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-z6xc6 has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-jr85n has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-96ht9 is running.
Starting Pipelinerun forgejo-mcp-code-scans-96ht9 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-96ht9 -fop1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-gcq9v is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-gcq9v in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-gcq9v -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-kzg42 is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-kzg42 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-kzg42 -fop1st Pipelines as Code/forgejo-mcp-code-scans-96ht9 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-gcq9v has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-kzg42 has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-8gm8h is running.
Starting Pipelinerun forgejo-mcp-code-scans-8gm8h in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-8gm8h -fop1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-b46d9 is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-b46d9 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-b46d9 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-6nvvk is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-6nvvk in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-6nvvk -fop1st Pipelines as Code/forgejo-mcp-code-scans-8gm8h has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-b46d9 has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-6nvvk has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-hz4xd is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-hz4xd in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-hz4xd -fop1st Pipelines as Code/forgejo-mcp-code-scans-95pf5 is running.
Starting Pipelinerun forgejo-mcp-code-scans-95pf5 in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-95pf5 -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-h4nxk is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-h4nxk in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-h4nxk -fop1st Pipelines as Code/forgejo-mcp-code-scans-95pf5 has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-hz4xd has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-h4nxk has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
op1st Pipelines as Code/forgejo-mcp-code-scans-hhf4t is running.
Starting Pipelinerun forgejo-mcp-code-scans-hhf4t in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-code-scans-hhf4t -fop1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-8rv5j is running.
Starting Pipelinerun forgejo-mcp-openspec-validate-pr-8rv5j in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-openspec-validate-pr-8rv5j -fop1st Pipelines as Code/forgejo-mcp-on-pull-request-xjg6v is running.
Starting Pipelinerun forgejo-mcp-on-pull-request-xjg6v in namespace op1st-pipelines
You can monitor the execution using the op1st Pipelines as Code PipelineRun viewer or through the command line by
using the tkn CLI with the following command:
tkn pr logs -n op1st-pipelines forgejo-mcp-on-pull-request-xjg6v -fop1st Pipelines as Code/forgejo-mcp-code-scans-hhf4t has successfully validated your commit.
Task Statuses:
fetch-source
gitleaks-version
gitleaks
op1st Pipelines as Code/forgejo-mcp-openspec-validate-pr-8rv5j has successfully validated your commit.
Task Statuses:
fetch-source
validate
op1st Pipelines as Code/forgejo-mcp-on-pull-request-xjg6v has successfully validated your commit.
Task Statuses:
fetch-source
build-and-test
commit-title-check
This PR delivers the OpenSpec change only — proposal, design, specs, and tasks. It does not implement any code and does not close any issues. Implementation and issue closure happen in follow-up PRs.