nemoclaw-maintainer-policies

Set the native GitHub Issue Type first, then add area labels only when the affected surface is clear, plus platform, provider, or integration labels only with direct evidence. Recommend Project Priority and Status separately, and show a dry run before any authorized write.

Apply exactly one PR type label: bug-fix, feature, refactor, or chore, based on evidence from the diff and commit prefixes. Add area labels for review routing, security for sensitive paths, and needs: rebase only when conflicts block review.

No. Issue version labels are tracking, regression-attention, or needs-PR coordination signals only. Release inclusion requires a PR that both carries the daily version label and is merged before the release cutoff.

Use needs: info only when missing details like reproduction steps, versions, or logs block work from proceeding. If the item can still be routed or reviewed, ask optional questions in questions_for_author without adding the label.

Agents may only create, apply, or delete labels inside the agt: * namespace within an authorized agent workflow. Unknown or unlisted canonical labels must be reported in an audit dry run, never created or applied.

It is read-only by default and cannot perform writes without an explicit authorization context. It also cannot answer questions outside the reference files, and it must not invent labels, statuses, or release states not defined in the taxonomy.