Harden daily workflows and simplify the public docs

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,5 +1,5 @@
 name: Bug report
-description: Report reproducible incorrect behavior, a crash, or an evidence-quality problem.
+description: Report a reproducible bug, crash, or misleading result.
 title: "[Bug]: "
 labels:
   - bug
@@ -21,8 +21,6 @@ body:
     attributes:
       label: Installation method
       options:
-        - Signed managed installer
-        - Signed portable ZIP
         - Built from source
         - Other
     validations:

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -1,35 +1,35 @@
 name: Feature request
-description: Propose a bounded defensive workflow or evidence improvement.
+description: Suggest a new workflow or improvement.
 title: "[Feature]: "
 labels:
   - enhancement
 body:
   - type: textarea
     id: problem
     attributes:
-      label: Operational problem
-      description: Describe the analyst or administrator task, not only the proposed implementation.
+      label: Problem to solve
+      description: Describe the analyst or administrator task, not just the implementation you have in mind.
     validations:
       required: true
   - type: textarea
     id: workflow
     attributes:
       label: Desired command and workflow
-      description: Include an example command, expected evidence, and automation exit behavior.
+      description: Include an example command, expected output, and automation exit behavior.
       render: powershell
     validations:
       required: true
   - type: textarea
     id: boundaries
     attributes:
-      label: Safety, privacy, and authorization boundaries
-      description: Explain network activity, privileges, sensitive data, destructive actions, and likely false claims.
+      label: Safety and privacy
+      description: Note any network activity, privileges, sensitive data, or destructive actions involved.
     validations:
       required: true
   - type: textarea
     id: alternatives
     attributes:
       label: Existing tools or alternatives
-      description: Name current tools and explain the specific gap PortCVE would fill.
+      description: Name any current tools and explain what PortCVE should do differently.
     validations:
       required: true

.github/pull_request_template.md

@@ -1,14 +1,14 @@
-## Purpose
+## What changed
 
-Describe the user-visible problem and the evidence contract this change affects.
+Explain the problem and the user-visible change.
 
 ## Safety and compatibility
 
-- [ ] No command gained implicit network access, privilege escalation, destructive behavior, or a weaker authorization gate.
-- [ ] Privacy-reduced output and `--include-private` behavior were reviewed.
-- [ ] Incomplete evidence still fails closed for `--strict` and finding gates.
-- [ ] Versioned JSON/schema or CLI compatibility changes are documented and tested.
-- [ ] New third-party actions and dependencies are pinned and justified.
+- [ ] Any new network access, privilege requirement, or destructive behavior is documented.
+- [ ] Default and `--include-private` output were reviewed for sensitive data.
+- [ ] `--strict` and finding gates still fail when required data is incomplete.
+- [ ] CLI or JSON schema changes are documented and tested.
+- [ ] New dependencies and GitHub Actions are pinned and justified.
 
 ## Verification
 
@@ -18,4 +18,4 @@ Describe the user-visible problem and the evidence contract this change affects.
 - [ ] `dotnet test PortCVE.sln -c Release --no-build --no-restore`
 - [ ] Relevant PowerShell/live harnesses passed, or the omission is explained below.
 
-Sanitized evidence and omitted gates:
+Notes, omitted checks, or sanitized test data:

CHANGELOG.md

@@ -16,8 +16,7 @@ All notable changes will be documented here. The project follows semantic versio
 - Added receipt-bound managed update, exact-version rollback, offline uninstall, guarded user-`PATH` changes, and transactional restoration tests; portable release ZIPs remain side-effect free.
 - Added cryptographic RFC 3161 token decoding, signer-info imprint binding, trusted TSA matching, full-SHA GitHub Actions pinning, release checksums, metadata, and provenance attestation.
 - Expanded CI to fresh Windows Server 2022 and 2025 runners with live loopback remote-assessment and enforceable performance budgets, plus local socket-churn and Docker-forwarding validation.
-- Added a daily-use runbook and structured privacy-aware issue and pull-request templates for expert feedback.
-- Live-validated Docker TCP/UDP correlation, the offline vulnerability path, and authorized adaptive HTTP discovery on a random loopback port; see `docs/validation.md` and `docs/remote-live-validation.md` for dated evidence and claim boundaries.
+- Live-validated Docker TCP/UDP correlation, the offline vulnerability path, and authorized adaptive HTTP discovery on a random loopback port; see `docs/validation.md` and `docs/remote-live-validation.md` for the dated results and limits.
 
 ## 0.1.0-alpha.1 - 2026-08-09