Restructure repository: migrate to v2 rewrite plan with catalog-first architecture

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,75 +1,91 @@
 name: Bug report
-description: Something is broken or behaves unexpectedly.
-labels: ["bug"]
+description: Something is broken or behaves incorrectly
+title: "[bug] "
+labels: ["bug", "triage"]
 body:
-  - type: textarea
-    id: summary
+  - type: markdown
     attributes:
-      label: Summary
-      description: One sentence — what's wrong?
-    validations:
-      required: true
+      value: |
+        Thanks for filing a bug. The more detail, the faster we can fix.
+
+        For security issues affecting flashing or signature verification,
+        do **not** file a public issue — see [SECURITY.md](../SECURITY.md).
 
   - type: textarea
-    id: repro
+    id: what-happened
     attributes:
-      label: Reproduction
-      description: |
-        Smallest steps to trigger the bug. Include component, adapter,
-        protocol, vehicle (year/make/model), and any relevant settings.
-      placeholder: |
-        1. Drop TOBDCircularGauge on a form
-        2. Set FramesPerSecond := 0
-        3. Run — gauge no longer updates after Value change
+      label: What happened?
+      description: A clear and concise description of the bug.
     validations:
       required: true
 
   - type: textarea
     id: expected
     attributes:
-      label: Expected behaviour
+      label: What did you expect to happen?
     validations:
       required: true
 
   - type: textarea
-    id: actual
+    id: repro
     attributes:
-      label: Actual behaviour
+      label: Steps to reproduce
+      description: Numbered steps. Minimal sample project welcome.
+      placeholder: |
+        1. Drop TOBDConnection on a form
+        2. Set Transport := otSerial, SerialSettings.Port := 'COM3'
+        3. Set Active := True
+        4. Observe …
     validations:
       required: true
 
   - type: input
-    id: delphi
+    id: delphi-version
     attributes:
       label: Delphi version
-      placeholder: "Delphi 12.1 Athens"
+      placeholder: "12 Athens / 11 Alexandria / 10.4 Sydney / 10.3 Rio"
     validations:
       required: true
 
   - type: input
-    id: skia
+    id: package-version
     attributes:
-      label: Skia4Delphi version
-      placeholder: "6.x"
+      label: Delphi-OBD version
+      placeholder: "v2.0.0-alpha.X / commit hash"
+    validations:
+      required: true
 
   - type: input
     id: os
     attributes:
-      label: OS
-      placeholder: "Windows 11 23H2"
+      label: Operating system
+      placeholder: "Windows 11 24H2 / Windows 10 22H2"
+    validations:
+      required: true
+
+  - type: input
+    id: adapter
+    attributes:
+      label: Adapter (chip + firmware)
+      description: If hardware is involved.
+      placeholder: "ELM327 v1.5 clone / OBDLink MX+ / J2534 PassThru"
+
+  - type: input
+    id: vehicle
+    attributes:
+      label: Vehicle (year, make, model, ECU)
+      description: If hardware is involved.
 
   - type: textarea
-    id: logs
+    id: log
     attributes:
-      label: Logs / stack trace
+      label: Captured log
+      description: |
+        A `.obdlog` capture from `TOBDRecorder` is the gold standard.
+        Attach the file or paste a relevant excerpt.
       render: text
 
-  - type: checkboxes
-    id: checks
+  - type: textarea
+    id: extra
     attributes:
-      label: Pre-flight
-      options:
-        - label: I searched existing issues and this isn't a duplicate.
-          required: true
-        - label: I'm on the latest tagged release (or `main`).
-          required: true
+      label: Anything else?

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,39 +1,52 @@
 name: Feature request
-description: Propose a new feature or extension.
-labels: ["enhancement"]
+description: Suggest a new feature, component, or catalogue addition
+title: "[feat] "
+labels: ["enhancement", "triage"]
 body:
+  - type: markdown
+    attributes:
+      value: |
+        Before opening, please skim [`PLAN.md`](../PLAN.md). If the feature
+        is already in scope for v1, tick the relevant box in your PR; if
+        it's a scope change, this issue is the right place to discuss it.
+
   - type: textarea
     id: problem
     attributes:
       label: What problem does this solve?
-      description: Describe the use case before the proposed solution.
+      description: User story shape — "as a developer building X I want Y so that Z".
     validations:
       required: true
 
   - type: textarea
     id: proposal
     attributes:
       label: Proposed solution
-      description: |
-        How should it work from a user's perspective? Pseudocode,
-        component sketches, API examples — whatever helps.
+      description: Component name, properties, events, methods if applicable.
     validations:
       required: true
 
   - type: textarea
     id: alternatives
     attributes:
       label: Alternatives considered
+    validations:
+      required: false
 
   - type: dropdown
-    id: roadmap
+    id: scope
     attributes:
-      label: Does this fit an existing roadmap milestone?
+      label: Scope impact
       options:
-        - "v2.1 Foundation"
-        - "v2.2 Components"
-        - "v2.3 Async & Logging"
-        - "v2.4 Distribution & Docs"
-        - "v2.5 Hardening"
-        - "v3.0 FMX & Mobile"
-        - "Backlog / not sure"
+        - "Within v1 scope (already in PLAN.md)"
+        - "Adds to v1 scope"
+        - "Post-1.0"
+        - "Not sure"
+    validations:
+      required: true
+
+  - type: input
+    id: spec
+    attributes:
+      label: Spec / standard reference
+      description: ISO / SAE / OEM document that backs the request, if any.

.github/PULL_REQUEST_TEMPLATE.md

@@ -9,18 +9,30 @@ doesn't apply, write "n/a".
 
 ## How did you test it?
 
-<!-- Bullet list. CI lint is not enough; tell us what you ran locally. -->
-
-- [ ] `tests/Tests.dpr` runs green
-- [ ] Manually exercised the affected components / examples
+- [ ] `tests/DelphiOBD_Tests.dpr` runs green
+- [ ] Manually exercised the affected components / samples
+- [ ] CI hygiene job is green (file headers, VCL/FMX guard, JSON lint)
 - [ ] N/A — explain:
 
-## Roadmap & changelog
+## Documentation
+
+Per [`STYLE.md`](../STYLE.md), every public symbol carries XMLDoc.
+
+- [ ] Every new or modified public type / method / property / event has
+      current XMLDoc
+- [ ] File headers updated (history block append-only)
+- [ ] [`PLAN.md`](../PLAN.md) updated if this PR affects scope or phasing
+- [ ] [`CHANGELOG.md`](../CHANGELOG.md) updated under `[Unreleased]`
+
+## Hardware risk (flashing / coding only)
+
+<!-- If this PR touches src/Flashing/, src/Coding/, src/Signature/, or
+the UDS write/transfer/memory components, fill these in. Otherwise
+delete this section. -->
 
-- [ ] Ticked the matching item in [`docs/ROADMAP.md`](../docs/ROADMAP.md)
-      (or this PR doesn't touch the roadmap)
-- [ ] Added an entry under `[Unreleased]` in [`CHANGELOG.md`](../CHANGELOG.md)
-      (or this PR is non-user-visible — explain)
+- [ ] Bench-tested on a real ECU. Vehicle / ECU model:
+- [ ] Tests cover the behaviour against captured fixtures (no live-ECU
+      dependency in CI)
 
 ## Reviewer notes