Provide native issue types in organization contributor defaults

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,18 @@
+name: Bug report
+description: Report a defect in this repository
+type: Bug
+body:
+  - type: textarea
+    id: behavior
+    attributes:
+      label: Expected and observed behavior
+      description: Describe the defect without including credentials or private source.
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction
+      description: Include minimal steps and the relevant version or environment.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,18 @@
+name: Feature request
+description: Propose a capability or improvement
+type: Feature
+body:
+  - type: textarea
+    id: outcome
+    attributes:
+      label: Desired outcome
+      description: Describe what should become possible without including private source.
+    validations:
+      required: true
+  - type: textarea
+    id: acceptance
+    attributes:
+      label: Acceptance and boundaries
+      description: Explain how to verify the outcome and what is outside the request.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/task.yml

@@ -0,0 +1,11 @@
+name: Task
+description: Track maintenance, investigation or qualification
+type: Task
+body:
+  - type: textarea
+    id: outcome
+    attributes:
+      label: Task outcome
+      description: Describe the work and its completion criteria without including private source.
+    validations:
+      required: true

CONTRIBUTING.md

@@ -0,0 +1,15 @@
+# Contributing to Clockgrove
+
+Read the target repository's README, AGENTS.md and contributor guidance before making a change. Search existing issues before opening a new one.
+
+Set the native GitHub issue type explicitly:
+
+- `Bug` for a standalone defect.
+- `Feature` for a requested capability or Factory Objective.
+- `Task` for a Work Item, maintenance, investigation or qualification. A corrective Work Item remains `Task`.
+
+Use labels for independent information such as area, priority, phase or Factory role. Do not add redundant `bug`, `enhancement`, `feature` or `task` classification labels. Preserve required role labels such as `factory:objective` and `factory:work-item`.
+
+Issue forms must set their top-level `type`. When creating an issue through a CLI or API, supply the type explicitly and verify the returned issue's type and labels. Do not assume a title or label assigned the type, and do not leave issues untyped when an appropriate native type is available.
+
+An issue's type or Project placement does not authorize execution, spending or deployment. Follow the target repository's existing approval and delivery rules. Keep credentials, private source and raw agent transcripts out of public issues.