Summary

Add an agent-ready NemoClaw maintainer workflow policy package so maintainers, engineers, and automation can share one reference for how this repo uses GitHub Issues, PRs, labels, Project fields, and the daily release train.

Problem

NemoClaw maintainers and agents need consistent guidance for triage and workflow decisions. Today, issue and PR velocity is high, multiple agents participate in the workflow, and policy knowledge can drift between repo skills, external tooling, and human practice.

Goals

• Add a reference-only maintainer policy skill package under .agents/skills/nemoclaw-maintainer-policies/.
• Document the source of truth for Issue Type, PR type labels, needs:* labels, Project Status/Priority/Effort/Sprint, and daily release labels.
• Provide machine-readable label taxonomy and workflow guidance for agents and apps that recommend or apply metadata.
• Update issue templates to use native GitHub Issue Type and current triage labels.
• Keep daily release labels as a first-class workflow for both PR release activation and issue-level daily attention.
• Avoid adding legacy .github/nvoss/community-manager policy files or migration notes.

Acceptance Criteria

• The maintainer policy package includes SKILL.md plus reference files for workflow policy, triage instructions, label taxonomy, Project workflow, daily flow, release train, and examples.
• SKILL.md is user-invocable and routes broad workflow questions and agent-implementation questions to the correct reference files.
• Issue templates set native Issue Type for bugs, enhancements, and documentation, and use the current triage queue label.
• The machine-readable taxonomy exposes allowed labels and Project field values needed by agents.
• References explain that PRs own daily release labels for release inclusion, while issues may also carry daily release labels when they need PR attention for the daily tag.
• No deprecated community-manager policy path, README, or CONTRIBUTING changes are included in the PR.