* docs: harden collaboration policy and review automation * ci(docs): remove unsupported lychee --exclude-mail flag * docs(governance): reduce automation side-effects and tighten risk controls * docs(governance): add backlog pruning and supersede protocol * docs(agents): codify engineering principles and risk-tier workflow * docs(readme): add centered star history section at bottom * docs(agents): enforce privacy-safe and neutral test wording * docs(governance): enforce privacy-safe and neutral collaboration checks * fix(ci): satisfy rustfmt and discord schema test fields * docs(governance): require ZeroClaw-native identity wording * docs(agents): add ZeroClaw identity-safe naming palette * docs(governance): codify code naming and architecture contracts * docs(contributing): add naming and architecture good/bad examples * docs(pr): reduce checkbox TODOs and shift to label-first metadata * docs(pr): remove duplicate collaboration track field * ci(labeler): auto-derive module labels and expand provider hints * ci(labeler): auto-apply trusted contributor on PRs and issues * fix(ci): apply rustfmt updates from latest main * ci(labels): flatten namespaces and add contributor tiers * chore: drop stale rustfmt-only drift * ci: scope Rust and docs checks by change set * ci: exclude non-markdown docs from docs-quality targets * ci: satisfy actionlint shellcheck output style * ci(labels): auto-correct manual contributor tier edits * ci(labeler): auto-correct risk label edits * ci(labeler): auto-correct size label edits --------- Co-authored-by: Chummy <183474434+chumyin@users.noreply.github.com>
107 lines
3 KiB
YAML
107 lines
3 KiB
YAML
name: Feature Request
|
|
description: Propose an improvement or new capability
|
|
title: "[Feature]: "
|
|
labels:
|
|
- enhancement
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for sharing your idea.
|
|
Please focus on user value, constraints, and rollout safety.
|
|
Do not include personal/sensitive data; use neutral project-scoped placeholders.
|
|
|
|
- type: input
|
|
id: summary
|
|
attributes:
|
|
label: Summary
|
|
description: One-line statement of the requested capability.
|
|
placeholder: Add a provider-level retry budget override for long-running channels.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem statement
|
|
description: What user pain does this solve and why is current behavior insufficient?
|
|
placeholder: Teams operating in unstable networks cannot tune retries per provider...
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: Proposed solution
|
|
description: Describe preferred behavior and interfaces.
|
|
placeholder: Add `[provider.retry]` config and enforce bounds in config validation.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: non_goals
|
|
attributes:
|
|
label: Non-goals / out of scope
|
|
description: Clarify what should not be included in the first iteration.
|
|
placeholder: No UI changes, no cross-provider dynamic adaptation in v1.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: What alternatives did you evaluate?
|
|
placeholder: Keep current behavior, use wrapper scripts, etc.
|
|
validations:
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: acceptance
|
|
attributes:
|
|
label: Acceptance criteria
|
|
description: What outcomes would make this request complete?
|
|
placeholder: |
|
|
- Config key is documented and validated
|
|
- Runtime path uses configured retry budget
|
|
- Regression tests cover fallback and invalid config
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: architecture
|
|
attributes:
|
|
label: Architecture impact
|
|
description: Which subsystem(s) are affected?
|
|
placeholder: providers/, channels/, memory/, runtime/, security/, docs/ ...
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: risk
|
|
attributes:
|
|
label: Risk and rollback
|
|
description: Main risk + how to disable/revert quickly.
|
|
placeholder: Risk is ... rollback is ...
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: breaking
|
|
attributes:
|
|
label: Breaking change?
|
|
options:
|
|
- No
|
|
- Yes
|
|
validations:
|
|
required: true
|
|
|
|
- type: checkboxes
|
|
id: hygiene
|
|
attributes:
|
|
label: Data hygiene checks
|
|
options:
|
|
- label: I removed personal/sensitive data from examples, payloads, and logs.
|
|
required: true
|
|
- label: I used neutral, project-focused wording and placeholders.
|
|
required: true
|