docs: strengthen collaboration governance and AGENTS engineering protocol (#263)

* 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>

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,12 +1,15 @@
 name: Bug Report
 description: Report a reproducible defect in ZeroClaw
 title: "[Bug]: "
+labels:
+  - bug
 body:
   - type: markdown
     attributes:
       value: |
         Thanks for taking the time to report a bug.
         Please provide a minimal reproducible case so maintainers can triage quickly.
+        Do not include personal/sensitive data; redact and anonymize all logs/payloads.
 
   - type: input
     id: summary
@@ -17,6 +20,34 @@ body:
     validations:
       required: true
 
+  - type: dropdown
+    id: component
+    attributes:
+      label: Affected component
+      options:
+        - runtime/daemon
+        - provider
+        - channel
+        - memory
+        - security/sandbox
+        - tooling/ci
+        - docs
+        - unknown
+    validations:
+      required: true
+
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      options:
+        - S0 - data loss / security risk
+        - S1 - workflow blocked
+        - S2 - degraded behavior
+        - S3 - minor issue
+    validations:
+      required: true
+
   - type: textarea
     id: current
     attributes:
@@ -48,11 +79,23 @@ body:
     validations:
       required: true
 
+  - type: textarea
+    id: impact
+    attributes:
+      label: Impact
+      description: Who is affected, how often, and practical consequences.
+      placeholder: |
+        Affected users: ...
+        Frequency: always/intermittent
+        Consequence: ...
+    validations:
+      required: true
+
   - type: textarea
     id: logs
     attributes:
       label: Logs / stack traces
-      description: Paste relevant logs (redact secrets).
+      description: Paste relevant logs (redact secrets, personal identifiers, and sensitive data).
       render: text
     validations:
       required: false
@@ -91,3 +134,15 @@ body:
         - No, first-time setup
     validations:
       required: true
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Pre-flight checks
+      options:
+        - label: I reproduced this on the latest main branch or latest release.
+          required: true
+        - label: I redacted secrets/tokens from logs.
+          required: true
+        - label: I removed personal identifiers and replaced identity-specific data with neutral placeholders.
+          required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,11 @@
 blank_issues_enabled: false
 contact_links:
   - name: Security vulnerability report
-    url: https://github.com/theonlyhennygod/zeroclaw/security/policy
+    url: https://github.com/zeroclaw-labs/zeroclaw/security/policy
     about: Please report security vulnerabilities privately via SECURITY.md policy.
   - name: Contribution guide
-    url: https://github.com/theonlyhennygod/zeroclaw/blob/main/CONTRIBUTING.md
+    url: https://github.com/zeroclaw-labs/zeroclaw/blob/main/CONTRIBUTING.md
     about: Please read contribution and PR requirements before opening an issue.
+  - name: PR workflow & reviewer expectations
+    url: https://github.com/zeroclaw-labs/zeroclaw/blob/main/docs/pr-workflow.md
+    about: Read risk-based PR tracks, CI gates, and merge criteria before filing feature requests.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,19 +1,31 @@
 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 problem are you trying to solve?
-      placeholder: Teams need a way to ...
+      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
 
@@ -21,8 +33,17 @@ body:
     id: proposal
     attributes:
       label: Proposed solution
-      description: Describe the preferred solution.
-      placeholder: Add a new subcommand / trait implementation ...
+      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
 
@@ -31,16 +52,28 @@ body:
     attributes:
       label: Alternatives considered
       description: What alternatives did you evaluate?
-      placeholder: Keep current behavior, use external tool, etc.
+      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/ ...
+      placeholder: providers/, channels/, memory/, runtime/, security/, docs/ ...
     validations:
       required: true
 
@@ -62,3 +95,13 @@ body:
         - 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