spec: forward-port pilot-driven normative snapshot onto Tool 0.2.2 main

[Kinirin]

Forward-ports the pilot-driven 0.2.0-draft normative snapshot onto the current Tool 0.2.2 main baseline (3aa5c0b0c91841b2a5eabba4aff1335703b832b1) without reverting Human Clarification.

Key migration decisions:

• preserve Tool/package 0.2.2 and its binding to specification revision 895e12d27230af2bb99ad17a96e8df8ef41bc3e0 until a later Tool explicitly rebinds;
• preserve ptsip clarify, deterministic zero-LLM clarification, GitHub origin detection, explicit GitHub-Issue publication, and external clarification state;
• forward-port PR spec: design next pilot-driven 0.2.0-draft normative snapshot #12 normative evidence/artifact/conformance work;
• keep boundaries XOR components for the canonical reference profile;
• replace PTSIP mandatory-rule exception/waiver semantics with a deterministic model: established MUST/MUST NOT violation => NON_CONFORMANT until remediation and reevaluation;
• retire/supersede PTSIP-EXC-001 in the new snapshot while preserving historical immutable revisions;
• reassign the previously planned Tool 0.2.1 evidence-correctness work package to Tool 0.2.3;
• keep Tool 0.3.0 as the capability/conformance expansion target.

The branch includes temporary self-removing migration workflows used only to apply and verify the corrective forward-port on this PR. They are removed by the migration result commit before merge.

This PR must not merge until Python 3.11-3.14 CI and the canonical spec-asset tests pass.

Post-merge CI usage optimization

After this PR merged as 14a0c2f54bb486de6a109979224f998b04fd04a3, main received follow-up CI-usage reductions. These do not change this normative snapshot or Tool semantics.

The latest optimization is commit e418b1382a7c87b952d7513b4b6c1a9ef68643b9 (ci: reduce tooling test action usage). The effective tooling-test policy is now:

• do not run the tooling test on PR creation, synchronization, or ordinary main pushes;
• when a tooling-sensitive PR targeting main is closed, run the test job only if the PR was actually merged;
• run again when a tool-v* Tool-version tag is pushed;
• test only Python 3.14 instead of the previous Python 3.11-3.14 matrix;
• keep the existing pytest, ptsip --version, and ptsip spec checks;
• retain per-ref concurrency cancellation so a superseded run does not continue consuming Actions time.

The earlier post-merge optimization commit 276da64fe696719a589f85d2c3be7e28c0eb852f introduced path filtering and same-ref cancellation; the later e418b1382a7c87b952d7513b4b6c1a9ef68643b9 commit supersedes its broader trigger/matrix policy.