Strengthen PR test trust baseline

.github/ISSUE_TEMPLATE/flaky-test.yml

@@ -0,0 +1,65 @@
+name: Flaky test
+description: Report a test that sometimes fails in PR, nightly, or manual CI.
+title: "[flaky] "
+labels: ["flaky-test", "test-trust"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Flaky tests must be isolated instead of left as "sometimes fails".
+        Include enough evidence to reproduce, quarantine, or stabilize the test.
+  - type: input
+    id: test-name
+    attributes:
+      label: Test name
+      description: Fully qualified test name when available.
+      placeholder: Unityctl.Core.Tests.Namespace.ClassName.TestName
+    validations:
+      required: true
+  - type: dropdown
+    id: suite
+    attributes:
+      label: Test suite
+      options:
+        - Unityctl.Shared.Tests
+        - Unityctl.Core.Tests
+        - Unityctl.Cli.Tests
+        - Unityctl.Mcp.Tests
+        - Unityctl.Integration.Tests
+        - Unity Integration workflow
+        - Other
+    validations:
+      required: true
+  - type: checkboxes
+    id: platforms
+    attributes:
+      label: Platforms observed
+      options:
+        - label: Linux
+        - label: macOS
+        - label: Windows
+        - label: Unity 2021.3.11f1
+        - label: Unity 6000.0.64f1
+  - type: textarea
+    id: ci-evidence
+    attributes:
+      label: CI evidence
+      description: Link the GitHub Actions run/job and paste the failing assertion or stack trace.
+      placeholder: https://github.com/Jason-hub-star/unityctl/actions/runs/...
+    validations:
+      required: true
+  - type: textarea
+    id: repeatability
+    attributes:
+      label: Repeatability
+      description: Include rerun count, whether a retry passed, and any timing/path/process/environment clues.
+      placeholder: Failed 1/5 on Windows; passes locally; timeout boundary near 1s.
+    validations:
+      required: true
+  - type: textarea
+    id: isolation-plan
+    attributes:
+      label: Isolation or stabilization plan
+      description: Describe the deterministic fixture, injected clock/delay/platform hook, skip/preflight, or quarantine issue needed.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/regression-bug.yml

@@ -0,0 +1,48 @@
+name: Regression bug
+description: Report a behavior regression that should get a reproduction test.
+title: "[regression] "
+labels: ["regression", "needs-repro-test"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Regression fixes should include a failing reproduction test in the same PR.
+        Prefer focused tests for IPC timeout, AppLocker, batch fallback, dirty scene policy, parser edge case, and command/schema/plugin drift.
+  - type: textarea
+    id: behavior
+    attributes:
+      label: Broken behavior
+      description: What changed, and what should have happened?
+    validations:
+      required: true
+  - type: dropdown
+    id: area
+    attributes:
+      label: Area
+      options:
+        - IPC timeout
+        - AppLocker
+        - batch fallback
+        - dirty scene policy
+        - parser edge case
+        - command/schema/plugin drift
+        - Unity live validation
+        - Other
+    validations:
+      required: true
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: Reproduction
+      description: Minimal command, project state, CI job, or fixture that demonstrates the bug.
+    validations:
+      required: true
+  - type: textarea
+    id: expected-test
+    attributes:
+      label: Required reproduction test
+      description: Name the test suite and the assertion that should fail before the fix and pass after it.
+      placeholder: tests/Unityctl.Cli.Tests/... should assert ...
+    validations:
+      required: true
+

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+## Summary
+
+- 
+
+## Test Trust Checklist
+
+- [ ] PR .NET gate stays green: Shared/Core/Cli/Mcp on Linux, macOS, and Windows.
+- [ ] Local focused tests were run for the changed layer(s).
+- [ ] No flaky test is left as "sometimes fails"; file `.github/ISSUE_TEMPLATE/flaky-test.yml` if isolation is still needed.
+- [ ] Bug fixes include a failing reproduction test, or link a `.github/ISSUE_TEMPLATE/regression-bug.yml` issue that explains the missing coverage.
+
+## Contract Safety Checklist
+
+For new or changed commands:
+
+- [ ] `WellKnownCommands` is updated in Shared and Plugin shared copy when needed.
+- [ ] `CommandCatalog` and schema/tool metadata are updated.
+- [ ] CLI registration in `src/Unityctl.Cli/Program.cs` is updated.
+- [ ] MCP `QueryTool`/`RunTool` allowlist/schema coverage is updated.
+- [ ] Plugin handler registration/coverage is updated.
+- [ ] CLI verb and Plugin handler command names do not duplicate or shadow another command.
+- [ ] `CommandSyncGuardrailTests` pass.
+
+## README User Path
+
+- [ ] Published CLI smoke remains covered: `dotnet tool install`, `unityctl tools --json`, `unityctl schema`, `doctor`, `check`, and `workflow verify`.
+- [ ] README/README.ko/docs describe any public surface or validation-scope change.
+
+## Unity Reality Check
+
+- [ ] PR intentionally uses fast .NET tests only, or Unity Integration was run manually/nightly.
+- [ ] If Unity Integration was run, artifacts were uploaded for the sample project validation.
+- [ ] If Unity Integration could not run, note whether `UNITY_LICENSE` or `UNITY_SERIAL` is missing and attach/check `license-preflight.txt` plus `planned-smoke.txt`.