Labels

origin/main carries commits absent from origin/dev

Waiting on platform work outside this repo; do not merge

Defect: incorrect or broken behavior vs documented contract

Maintenance: CI, tooling, templates, housekeeping (not a feature)

Dependency bump (Dependabot or equivalent)

Docs, skills, README, or in-repo guides only (no runtime change)

New capability or intentional behavior change (not a bugfix)

Scoped for a first-time contributor; acceptance criteria are clear

Maintainers want external help; design direction is settled

Hosted / remote MCP profile (multi-user, on-behalf-of, auth surface)

Urgent fix for production/hosted; prioritize over normal queue

Waiting on reporter for more information

Maintainer needs to evaluate this issue

Logs, metrics, traces, or client telemetry (User-Agent, headers)

Address data correctness or the highest-risk evidence gap first.

Prioritize diagnosis, capabilities, dependencies, and product decisions.

Schedule maintenance and convenience work after higher-risk items.

Pull requests that update python:uv code

Clarification needed; not yet a confirmed bug or feature

Fully specified, ready for an AFK agent

Requires human implementation

Internal restructure with no intended user-facing behavior change

Version bump, tag, and GitHub Release cut (release PR from rc-main/release/* into main)

Correctness under failure: retries, idempotency, false errors, resilience

Hardening fix for a weakness. Report an unfixed vulnerability privately (SECURITY.md)

Resolve scope, compatibility, ownership, or a prerequisite before implementation.

A bounded next change has evidence. Remaining acceptance still applies.

Run a targeted test, measurement, or delivery review before choosing a change.

Will not be actioned