.github/ISSUE_TEMPLATE/config.yml

@@ -1,12 +0,0 @@
-# The new-issue interception (issue #24, decision 1): interception over
-# instruction — prose alone has already proven insufficient everywhere else
-# in this org. Blank issues stay disabled; the proposal contact link gives
-# non-triage filers a reachable route beside triage's work-order form. That
-# chooser is native forge behavior, no automation needed.
-blank_issues_enabled: false
-contact_links:
-  - name: Ideas, bugs, questions — file a Proposal
-    url: https://forgejo.heavyduty.builders/heavy-duty/stoke/issues/new?template=proposal.yml
-    about: >-
-      Anyone may file a proposal. Triage converts it into a work issue or
-      refuses it with reasons; only triage mints work issues (TRIAGE.md).

.github/ISSUE_TEMPLATE/proposal.yml

@@ -1,34 +0,0 @@
-# This intake form applies no labels: queue labels are triage's explicit act
-# (LABELS.md), and the issue-flow sweep catches non-triage authors, so the form
-# must not pre-judge the proposal's queue state (#24 D2).
-name: Proposal (anyone)
-description: >-
-  Share an idea, bug, question, or rough "we should…" for triage to convert
-  into work or refuse with reasons.
-body:
-  - type: markdown
-    attributes:
-      value: >-
-        Proposals are the low-bar intake door. Say what you noticed and why it
-        might matter; triage will decide whether it becomes a work issue.
-  - type: textarea
-    id: noticed
-    attributes:
-      label: What did you notice?
-      description: A rough idea, bug, question, or "we should…" is enough.
-    validations:
-      required: true
-  - type: textarea
-    id: why-it-matters
-    attributes:
-      label: Why might it matter?
-      description: Optional — describe the impact or opportunity if you can.
-    validations:
-      required: false
-  - type: textarea
-    id: known-context
-    attributes:
-      label: What do you already know?
-      description: Optional — add links, examples, constraints, or prior art.
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/work-order.yml

@@ -1,75 +0,0 @@
-# The issue contract (TRIAGE.md "The issue contract") as a form, so every
-# minted issue lands with the same bones and a later parser (#18) can key on
-# stable section headings. Consistency, not a gate: the form applies no
-# labels — queue labels are triage's explicit act (LABELS.md), and #18's
-# sweep is what catches non-triage authors, so the form must not pre-judge
-# that (issue #24, decision 2).
-name: Work order (triage only)
-description: >-
-  The issue contract (TRIAGE.md) as a form. Only triage mints work issues —
-  everyone else files a proposal. Triage may still compose by hand when
-  the form fights it: `stoke issue create --body-file` bypasses forms and stays
-  legitimate for the triage identity.
-body:
-  - type: markdown
-    attributes:
-      value: >-
-        **The title names the deliverable** — "lib/version.sh — one version
-        abstraction, two backends", never "improve version handling". The
-        bar for everything below, stated once: a competent builder who has
-        read only this issue and the repo can succeed (TRIAGE.md). Labels
-        (type, `scope:*`, `ready`/`blocked`) are your explicit act after
-        minting — this form applies none.
-  - type: textarea
-    id: context
-    attributes:
-      label: Context
-      description: >-
-        Why this exists, with links — the proposal it came from, the code
-        it touches (permalinks at a pinned SHA, so line references cannot
-        rot), prior art in sibling repos.
-    validations:
-      required: true
-  - type: textarea
-    id: spec
-    attributes:
-      label: Spec
-      description: >-
-        Decisions made, not options listed. If the spec still has an open
-        question, the issue is not ready to exist.
-    validations:
-      required: true
-  - type: textarea
-    id: tasks
-    attributes:
-      label: Tasks
-      description: The steps, checkboxed, in order.
-      placeholder: "- [ ] the first step"
-    validations:
-      required: true
-  - type: textarea
-    id: acceptance-criteria
-    attributes:
-      label: Acceptance criteria
-      description: >-
-        Checkboxed, verifiable, and honest — these become the builder's
-        definition of done and the reviewer's review spec, verbatim.
-      placeholder: "- [ ] a verifiable outcome"
-    validations:
-      required: true
-  - type: textarea
-    id: test-plan
-    attributes:
-      label: Test plan
-      description: What proves it, including the cases that must fail.
-    validations:
-      required: true
-  - type: textarea
-    id: dependencies
-    attributes:
-      label: Dependencies
-      description: >-
-        `Blocked by #N` / `Blocks #N`, and `Part of #E` when an epic
-        organizes it — or state "None".
-    validations:
-      required: true

CONTRIBUTING.md

@@ -51,6 +51,5 @@ the ruling's alternatives.
 
 ## Work issue ownership
 
-Only triage mints work issues; anyone may file a
+Only triage mints work issues; anyone may file a proposal, which triage converts
-[proposal](https://forgejo.heavyduty.builders/heavy-duty/stoke/issues/new?template=proposal.yml),
+or refuses.
-which triage converts or refuses.

changelog.d/50.md

@@ -1 +0,0 @@
-- Added guided proposal and triage work-order forms, with the contributor guide linking directly to proposal intake. (#50).