PTSIP 0.3.8a2__tar.gz → 0.3.8a4__tar.gz

ptsip-0.3.8a4/MANIFEST.in

@@ -0,0 +1,5 @@
+prune src/tests
+recursive-include src/policy *.yaml *.json
+recursive-include src/ptsip/profiles *.ptsip.yaml
+include src/ptsip/profiles/index.yaml
+include registry/project-profile-contracts.yaml

{ptsip-0.3.8a2 → ptsip-0.3.8a4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: PTSIP
-Version: 0.3.8a2
+Version: 0.3.8a4
 Summary: Reference tooling for primary lifecycle ownership and responsibility isolation
 Author: Kinirin
 Maintainer: Kinirin
@@ -37,13 +37,13 @@ Requires-Dist: setuptools>=77.0.3; extra == "dev"
 Dynamic: license-file
 
 <p align="right">
-  English | <a href="README.ko.md">한국어</a>
+  English | <a href="docs/translated/README.ko.md">한국어</a>
 </p>
 
 # PTSIP — Primary Lifecycle Ownership and Responsibility Isolation Policy
 
-**Status:** Tool `0.3.8a2` repository-namespace stabilization prerelease — publication pending<br>
-**Tool/package version:** `0.3.8a2`<br>
+**Status:** Tool `0.3.8a4` Go-native developer automation and release-verification consolidation prerelease — publication pending<br>
+**Tool/package version:** `0.3.8a4`<br>
 **Project Profile contract:** `pp.1.02`<br>
 **Specification family:** `0.3.7-draft`<br>
 **Bound immutable Specification revision:** `3c47816770d194ae42f98faedc911d980db0e62a`<br>
@@ -55,11 +55,11 @@ PTSIP is a project-defined architecture policy for separating project responsibi
 
 > **Purpose precedes reuse.** Classify a coherent responsibility by why it exists and which lifecycle owns it before optimizing for code sharing.
 
-Tool `0.3.8a2` is a repository-namespace stabilization prerelease built on the already-published `0.3.8a1` bridge and the same frozen Specification binding. It preserves the proposed-candidate bridge while establishing `.ptsip/` as the canonical repository-local ownership boundary for PTSIP-managed contracts, registries, configuration, task/operation metadata, and execution state. Canonical repository indexes use JSON. This release reserves Task and runtime namespaces but does not claim a completed generic Task Engine, Go runtime, or Tool `0.4.0` capability-recovery implementation.
+Tool `0.3.8a4` consolidates the developer control plane built after `0.3.8a3`: native Go developer automation, Root Family policy lifecycle enforcement, canonical Project Profile storage, deterministic Test Mode routing, and a single release workflow with responsibility-separated Go release verification. The `0.3.8a3` Consumer Context Plane behavior remains available. The Specification family and Project Profile contract identities remain unchanged.
 
 ## Primary lifecycle ownership
 
-Canonical Tool `0.3.8a2` classifications remain exactly:
+Canonical Tool `0.3.8a4` classifications remain exactly:
 
 | Classification | Meaning |
 | --- | --- |
@@ -81,9 +81,9 @@ TOOLCHAIN
 NEUTRAL_CONTRACT
 ```
 
-Tool `0.3.8a2` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
+Tool `0.3.8a4` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
 
-Tool `0.3.8a2` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
+Tool `0.3.8a4` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
 
 ## Classification is not path or technology
 
@@ -104,7 +104,7 @@ Paths such as `tests/`, `tools/`, `deploy/`, `ops/`, or `.github/workflows/` are
 
 ## Responsibility Map v2
 
-Tool `0.3.8a2` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
+Tool `0.3.8a4` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
 
 ```text
 classification
@@ -233,12 +233,12 @@ Upgrade to the latest **published** release:
 python -m pip install --upgrade PTSIP
 ```
 
-Tool `0.3.8a2` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
+Tool `0.3.8a4` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
 
 After publication, install this prerelease explicitly with:
 
 ```powershell
-python -m pip install "PTSIP==0.3.8a2"
+python -m pip install "PTSIP==0.3.8a4"
 ```
 
 For source development on this release line:
@@ -261,15 +261,26 @@ ptsip clarify .
 ptsip gate .
 ptsip resolve --help
 ptsip conform .
+ptsip context status . --json
+ptsip context check . --json
 ```
 
 New project-owned profiles are selected through `.ptsip/profiles/index.json`; the catalog's `default_profile` resolves the active `*.ptsip.yaml` resource. Repository-root `ptsip.yaml` remains a compatibility/migration input, and an explicit `--profile` path still takes precedence.
 
+PTSIP developers use that same local catalog and `.ptsip/profiles/main.ptsip.yaml`.
+Profile implementation modules and distributed examples live in
+`src/ptsip/profiles/`. The public catalog is `src/ptsip/profiles/index.yaml`;
+`registry/project-profile-contracts.yaml` explicitly binds this source layout.
+Historical PP baselines under `src/ptsip/profiles/history/` are preserved in
+source distributions for verification and are excluded from wheels. Moving
+storage preserves PP identity and historical bytes; public profile or schema
+semantic changes still require the native Go PP transition gates.
+
 ## Adoption and decision authority
 
 Repository evidence is not architecture authority. Candidate discovery, path names, templates, heuristics, and agent confidence can support review but cannot manufacture project intent.
 
-Canonical Tool `0.3.8a2` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
+Canonical Tool `0.3.8a4` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
 
 ```text
 classification
@@ -279,7 +290,7 @@ runtime_required
 executable
 ```
 
-The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a2` ownership authority.
+The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a4` ownership authority.
 
 Example dry-run:
 
@@ -344,9 +355,9 @@ PTSIP uses action-time synchronization rather than continuous background polling
 
 Artifact ownership is independent from producer ownership. A `DEVELOPMENT_TOOLING` or `DELIVERY` component may validly build a `PRODUCT` artifact, but the resulting artifact must still satisfy the Product package boundary.
 
-Tool `0.3.8a2` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
+Tool `0.3.8a4` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
 
-## VPMS — Verification Purpose Management System
+## VPMS — Verification Protocol Management System
 
 PTSIP and VPMS answer different questions:
 
@@ -355,12 +366,32 @@ PTSIP
     Who owns this responsibility across its lifecycle?
 
 VPMS
-    Why does this Verification Case exist, and what does it protect?
+    How are explicit Verification Cases bound, executed, and reported?
 ```
 
-PTSIP classification and VPMS Verification Purpose remain separate axes. PTSIP core does not depend on VPMS. VPMS consumes only a narrow read-only projection of already-resolved PTSIP metadata.
+PTSIP classification and the historical VPMS Verification Purpose remain separate axes. The Case `purpose` field is compatibility-only: it does not decide selection, runner binding, or PTSIP classification. PTSIP core does not depend on VPMS.
+
+The repository's three product contracts are ACTIVE and separately own the Case/reference/runner protocol, explicit Case selection, and execution composition. The public API is:
+
+```python
+from vpms import load_registry_snapshot, resolve_selection, run_cases
+
+loaded = load_registry_snapshot(case_definitions, references=reference_registrations)
+if not loaded.ok:
+    raise ValueError(loaded.diagnostics)
+selection = resolve_selection(
+    loaded.snapshot, {"kind": "CASE_IDS", "case_ids": ["explicit.case.id"]}
+)
+if not selection.ok:
+    raise ValueError(selection.diagnostics)
+results = run_cases(loaded.snapshot, selection, executors=runner_adapters)
+```
+
+`case_definitions`, `reference_registrations`, and `runner_adapters` are explicit caller-owned inputs. Selection fails closed on invalid, duplicate, or unknown IDs. Execution accepts selection bound to the same validated snapshot and preflights every selected adapter before executing the first Case. `SelectionScope`, `select_cases`, and `run_selected_cases` are retired, not compatibility aliases.
+
+Optional PTSIP integration uses `ptsip.validation.handoff.load_validated_effective_map` followed by `vpms.integration.ptsip_bridge.metadata_from_effective_map`. ACTIVE `SFP-0023` owns only this read-only boundary: the projection exposes exact component ID and classification from a genuinely validated immutable effective map. A raw dict, a `validated=True` assertion, and the historical `load_ptsip_metadata` compatibility reader are not canonical validation proof or implicit fallbacks. `SFP-0006` is RETIRED with its historical meaning preserved; VPMS product protocol authority resides in the separate product contracts.
 
-The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a2` PTSIP classification.
+The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a4` PTSIP classification.
 
 VPMS verification PASS does not imply PTSIP `CONFORMANT`, and PTSIP `CONFORMANT` does not imply functional verification PASS.
 
@@ -431,6 +462,34 @@ in its Tool release note; advancing the PP contract does not rewrite that Tool h
 
 A new immutable revision is required only for a genuine normative change. Release workflow, test, planning, status, or documentation-only changes do not move `SPEC_REVISION` by themselves.
 
+## Tool 0.3.8a4 release identity
+
+Tool `0.3.8a4` consolidates native Go developer automation, Root Family policy lifecycle enforcement, canonical Project Profile storage, Test Mode routing, and release verification without changing the bound Specification family or Project Profile contract.
+
+```text
+Tool:             0.3.8a4
+Project Profile:  pp.1.02
+Specification:    0.3.7-draft
+SPEC_REVISION:    3c47816770d194ae42f98faedc911d980db0e62a
+Release scope:    Go-native developer control plane + responsibility-separated release verification
+```
+
+Release preparation and publication use the single `.github/workflows/tooling-release.yml` surface. PREPARE and PUBLISH retain independent exact-source verification. Release readiness is owned by the Go tests under `developer/tests/release/`.
+
+## Tool 0.3.8a3 release identity
+
+Tool `0.3.8a3` is an emergency Context Plane migration-semantics patch over the published `0.3.8a2` repository-namespace release.
+
+```text
+Tool:             0.3.8a3
+Project Profile:  pp.1.02
+Specification:    0.3.7-draft
+SPEC_REVISION:    3c47816770d194ae42f98faedc911d980db0e62a
+Release scope:    deterministic MEMORY.md -> Context Plane migration and projection repair
+```
+
+The canonical semantic write target is `.ptsip/context/source/context.source.json`. Generated `context.json`, `context.jsonl`, and `context.schema.json` are repaired from that source. Semantic ambiguity remains user-owned; deterministic projection repair is preauthorized for coding agents. Unlike Tool `0.3.8a2`, Tool `0.3.8a3` ships this implementation inside the Consumer Tool as `ptsip/context_plane.py`; a release build is invalid if that module or the `ptsip context` CLI surface is absent from the built wheel.
+
 ## Tool 0.3.8a2 release identity
 
 Tool `0.3.8a2` is a repository-namespace stabilization prerelease with a deliberately narrow compatibility goal.
@@ -465,7 +524,7 @@ This Tool release does not introduce a new Specification family or Project Profi
 
 It adds support for representing a not-yet-existing component as an explicit proposed candidate and resolving that proposal without silently materializing it as an active component. It does not claim completion of the broader Tool `0.4.0` capability-recovery architecture.
 
-Release scope and verification history are recorded in [`releasenote/tool/0.3.8a1.md`](releasenote/tool/0.3.8a1.md). The release gate is defined by [`planning/0.3.8/0.3.8a1-emergency-release-gate.yaml`](planning/0.3.8/0.3.8a1-emergency-release-gate.yaml).
+Release scope and verification history are recorded in [`releasenote/tool/0.3.8a1.md`](releasenote/tool/0.3.8a1.md). The release gate is defined by [`developer/planning/0.3.8/0.3.8a1/0.3.8a1-emergency-release-gate.yaml`](developer/planning/0.3.8/0.3.8a1/0.3.8a1-emergency-release-gate.yaml).
 
 ## License authority
 
@@ -482,8 +541,8 @@ Read-only inspection and Pilot operations remain read-only and do not create rep
 
 Repository tooling implementations may physically live under `tools/`, `scripts/`, `src/`, or another project-owned path. Their PTSIP-owned registration, policy bindings, task/operation contracts, indexes, and lifecycle state must not establish an alternative repository-local PTSIP control-plane root.
 
-Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a2` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
+Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a4` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
 
 ## Project status
 
-PTSIP remains experimental. Tool `0.3.8a2` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a2.md`](releasenote/tool/0.3.8a2.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).
+PTSIP remains experimental. Tool `0.3.8a4` is the current Go-native developer automation and release-verification consolidation prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a4.md`](releasenote/tool/0.3.8a4.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).

{ptsip-0.3.8a2 → ptsip-0.3.8a4}/README.md

@@ -1,11 +1,11 @@
 <p align="right">
-  English | <a href="README.ko.md">한국어</a>
+  English | <a href="docs/translated/README.ko.md">한국어</a>
 </p>
 
 # PTSIP — Primary Lifecycle Ownership and Responsibility Isolation Policy
 
-**Status:** Tool `0.3.8a2` repository-namespace stabilization prerelease — publication pending<br>
-**Tool/package version:** `0.3.8a2`<br>
+**Status:** Tool `0.3.8a4` Go-native developer automation and release-verification consolidation prerelease — publication pending<br>
+**Tool/package version:** `0.3.8a4`<br>
 **Project Profile contract:** `pp.1.02`<br>
 **Specification family:** `0.3.7-draft`<br>
 **Bound immutable Specification revision:** `3c47816770d194ae42f98faedc911d980db0e62a`<br>
@@ -17,11 +17,11 @@ PTSIP is a project-defined architecture policy for separating project responsibi
 
 > **Purpose precedes reuse.** Classify a coherent responsibility by why it exists and which lifecycle owns it before optimizing for code sharing.
 
-Tool `0.3.8a2` is a repository-namespace stabilization prerelease built on the already-published `0.3.8a1` bridge and the same frozen Specification binding. It preserves the proposed-candidate bridge while establishing `.ptsip/` as the canonical repository-local ownership boundary for PTSIP-managed contracts, registries, configuration, task/operation metadata, and execution state. Canonical repository indexes use JSON. This release reserves Task and runtime namespaces but does not claim a completed generic Task Engine, Go runtime, or Tool `0.4.0` capability-recovery implementation.
+Tool `0.3.8a4` consolidates the developer control plane built after `0.3.8a3`: native Go developer automation, Root Family policy lifecycle enforcement, canonical Project Profile storage, deterministic Test Mode routing, and a single release workflow with responsibility-separated Go release verification. The `0.3.8a3` Consumer Context Plane behavior remains available. The Specification family and Project Profile contract identities remain unchanged.
 
 ## Primary lifecycle ownership
 
-Canonical Tool `0.3.8a2` classifications remain exactly:
+Canonical Tool `0.3.8a4` classifications remain exactly:
 
 | Classification | Meaning |
 | --- | --- |
@@ -43,9 +43,9 @@ TOOLCHAIN
 NEUTRAL_CONTRACT
 ```
 
-Tool `0.3.8a2` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
+Tool `0.3.8a4` preserves the five-classification model established by Tool `0.3.6`. `TOOLCHAIN` is therefore **legacy Tool `0.3.5` input**, not a current canonical alias. A legacy Toolchain responsibility may become `DEVELOPMENT_TOOLING`, `DELIVERY`, `OPERATIONS`, or require a split depending on its actual lifecycle ownership. Blind `TOOLCHAIN -> DEVELOPMENT_TOOLING` rewriting is prohibited.
 
-Tool `0.3.8a2` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
+Tool `0.3.8a4` provides evidence-bound direct current-target migration for explicitly supported historical sources. Migration capability remains separate from repository adoption authority and never turns inference into project intent.
 
 ## Classification is not path or technology
 
@@ -66,7 +66,7 @@ Paths such as `tests/`, `tools/`, `deploy/`, `ops/`, or `.github/workflows/` are
 
 ## Responsibility Map v2
 
-Tool `0.3.8a2` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
+Tool `0.3.8a4` uses Responsibility Map v2 as the project-owned architecture declaration model. It keeps several axes independent:
 
 ```text
 classification
@@ -195,12 +195,12 @@ Upgrade to the latest **published** release:
 python -m pip install --upgrade PTSIP
 ```
 
-Tool `0.3.8a2` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
+Tool `0.3.8a4` is a prerelease. A normal `pip install PTSIP` may continue to select the latest stable release unless prereleases are explicitly requested.
 
 After publication, install this prerelease explicitly with:
 
 ```powershell
-python -m pip install "PTSIP==0.3.8a2"
+python -m pip install "PTSIP==0.3.8a4"
 ```
 
 For source development on this release line:
@@ -223,15 +223,26 @@ ptsip clarify .
 ptsip gate .
 ptsip resolve --help
 ptsip conform .
+ptsip context status . --json
+ptsip context check . --json
 ```
 
 New project-owned profiles are selected through `.ptsip/profiles/index.json`; the catalog's `default_profile` resolves the active `*.ptsip.yaml` resource. Repository-root `ptsip.yaml` remains a compatibility/migration input, and an explicit `--profile` path still takes precedence.
 
+PTSIP developers use that same local catalog and `.ptsip/profiles/main.ptsip.yaml`.
+Profile implementation modules and distributed examples live in
+`src/ptsip/profiles/`. The public catalog is `src/ptsip/profiles/index.yaml`;
+`registry/project-profile-contracts.yaml` explicitly binds this source layout.
+Historical PP baselines under `src/ptsip/profiles/history/` are preserved in
+source distributions for verification and are excluded from wheels. Moving
+storage preserves PP identity and historical bytes; public profile or schema
+semantic changes still require the native Go PP transition gates.
+
 ## Adoption and decision authority
 
 Repository evidence is not architecture authority. Candidate discovery, path names, templates, heuristics, and agent confidence can support review but cannot manufacture project intent.
 
-Canonical Tool `0.3.8a2` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
+Canonical Tool `0.3.8a4` explicit adoption facts center on `classification` as lifecycle ownership authority. New canonical decisions use facts such as:
 
 ```text
 classification
@@ -241,7 +252,7 @@ runtime_required
 executable
 ```
 
-The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a2` ownership authority.
+The historical `lifecycle_owner` field is legacy migration evidence, not a second Tool `0.3.8a4` ownership authority.
 
 Example dry-run:
 
@@ -306,9 +317,9 @@ PTSIP uses action-time synchronization rather than continuous background polling
 
 Artifact ownership is independent from producer ownership. A `DEVELOPMENT_TOOLING` or `DELIVERY` component may validly build a `PRODUCT` artifact, but the resulting artifact must still satisfy the Product package boundary.
 
-Tool `0.3.8a2` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
+Tool `0.3.8a4` supports snapshot-bound Product Artifact evidence. Release verification checks actual built distribution content rather than treating packaging configuration as proof. Product distribution verification rejects definite non-Product implementation leakage under `PTSIP-PKG-001`.
 
-## VPMS — Verification Purpose Management System
+## VPMS — Verification Protocol Management System
 
 PTSIP and VPMS answer different questions:
 
@@ -317,12 +328,32 @@ PTSIP
     Who owns this responsibility across its lifecycle?
 
 VPMS
-    Why does this Verification Case exist, and what does it protect?
+    How are explicit Verification Cases bound, executed, and reported?
 ```
 
-PTSIP classification and VPMS Verification Purpose remain separate axes. PTSIP core does not depend on VPMS. VPMS consumes only a narrow read-only projection of already-resolved PTSIP metadata.
+PTSIP classification and the historical VPMS Verification Purpose remain separate axes. The Case `purpose` field is compatibility-only: it does not decide selection, runner binding, or PTSIP classification. PTSIP core does not depend on VPMS.
+
+The repository's three product contracts are ACTIVE and separately own the Case/reference/runner protocol, explicit Case selection, and execution composition. The public API is:
+
+```python
+from vpms import load_registry_snapshot, resolve_selection, run_cases
+
+loaded = load_registry_snapshot(case_definitions, references=reference_registrations)
+if not loaded.ok:
+    raise ValueError(loaded.diagnostics)
+selection = resolve_selection(
+    loaded.snapshot, {"kind": "CASE_IDS", "case_ids": ["explicit.case.id"]}
+)
+if not selection.ok:
+    raise ValueError(selection.diagnostics)
+results = run_cases(loaded.snapshot, selection, executors=runner_adapters)
+```
+
+`case_definitions`, `reference_registrations`, and `runner_adapters` are explicit caller-owned inputs. Selection fails closed on invalid, duplicate, or unknown IDs. Execution accepts selection bound to the same validated snapshot and preflights every selected adapter before executing the first Case. `SelectionScope`, `select_cases`, and `run_selected_cases` are retired, not compatibility aliases.
+
+Optional PTSIP integration uses `ptsip.validation.handoff.load_validated_effective_map` followed by `vpms.integration.ptsip_bridge.metadata_from_effective_map`. ACTIVE `SFP-0023` owns only this read-only boundary: the projection exposes exact component ID and classification from a genuinely validated immutable effective map. A raw dict, a `validated=True` assertion, and the historical `load_ptsip_metadata` compatibility reader are not canonical validation proof or implicit fallbacks. `SFP-0006` is RETIRED with its historical meaning preserved; VPMS product protocol authority resides in the separate product contracts.
 
-The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a2` PTSIP classification.
+The current VPMS compatibility vocabulary may still contain `PRODUCT | TOOLCHAIN`. VPMS `TOOLCHAIN` is not a canonical Tool `0.3.8a4` PTSIP classification.
 
 VPMS verification PASS does not imply PTSIP `CONFORMANT`, and PTSIP `CONFORMANT` does not imply functional verification PASS.
 
@@ -393,6 +424,34 @@ in its Tool release note; advancing the PP contract does not rewrite that Tool h
 
 A new immutable revision is required only for a genuine normative change. Release workflow, test, planning, status, or documentation-only changes do not move `SPEC_REVISION` by themselves.
 
+## Tool 0.3.8a4 release identity
+
+Tool `0.3.8a4` consolidates native Go developer automation, Root Family policy lifecycle enforcement, canonical Project Profile storage, Test Mode routing, and release verification without changing the bound Specification family or Project Profile contract.
+
+```text
+Tool:             0.3.8a4
+Project Profile:  pp.1.02
+Specification:    0.3.7-draft
+SPEC_REVISION:    3c47816770d194ae42f98faedc911d980db0e62a
+Release scope:    Go-native developer control plane + responsibility-separated release verification
+```
+
+Release preparation and publication use the single `.github/workflows/tooling-release.yml` surface. PREPARE and PUBLISH retain independent exact-source verification. Release readiness is owned by the Go tests under `developer/tests/release/`.
+
+## Tool 0.3.8a3 release identity
+
+Tool `0.3.8a3` is an emergency Context Plane migration-semantics patch over the published `0.3.8a2` repository-namespace release.
+
+```text
+Tool:             0.3.8a3
+Project Profile:  pp.1.02
+Specification:    0.3.7-draft
+SPEC_REVISION:    3c47816770d194ae42f98faedc911d980db0e62a
+Release scope:    deterministic MEMORY.md -> Context Plane migration and projection repair
+```
+
+The canonical semantic write target is `.ptsip/context/source/context.source.json`. Generated `context.json`, `context.jsonl`, and `context.schema.json` are repaired from that source. Semantic ambiguity remains user-owned; deterministic projection repair is preauthorized for coding agents. Unlike Tool `0.3.8a2`, Tool `0.3.8a3` ships this implementation inside the Consumer Tool as `ptsip/context_plane.py`; a release build is invalid if that module or the `ptsip context` CLI surface is absent from the built wheel.
+
 ## Tool 0.3.8a2 release identity
 
 Tool `0.3.8a2` is a repository-namespace stabilization prerelease with a deliberately narrow compatibility goal.
@@ -427,7 +486,7 @@ This Tool release does not introduce a new Specification family or Project Profi
 
 It adds support for representing a not-yet-existing component as an explicit proposed candidate and resolving that proposal without silently materializing it as an active component. It does not claim completion of the broader Tool `0.4.0` capability-recovery architecture.
 
-Release scope and verification history are recorded in [`releasenote/tool/0.3.8a1.md`](releasenote/tool/0.3.8a1.md). The release gate is defined by [`planning/0.3.8/0.3.8a1-emergency-release-gate.yaml`](planning/0.3.8/0.3.8a1-emergency-release-gate.yaml).
+Release scope and verification history are recorded in [`releasenote/tool/0.3.8a1.md`](releasenote/tool/0.3.8a1.md). The release gate is defined by [`developer/planning/0.3.8/0.3.8a1/0.3.8a1-emergency-release-gate.yaml`](developer/planning/0.3.8/0.3.8a1/0.3.8a1-emergency-release-gate.yaml).
 
 ## License authority
 
@@ -444,8 +503,8 @@ Read-only inspection and Pilot operations remain read-only and do not create rep
 
 Repository tooling implementations may physically live under `tools/`, `scripts/`, `src/`, or another project-owned path. Their PTSIP-owned registration, policy bindings, task/operation contracts, indexes, and lifecycle state must not establish an alternative repository-local PTSIP control-plane root.
 
-Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a2` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
+Canonical machine indexes under `.ptsip/` use JSON. Tool `0.3.8a4` uses `.ptsip/index.json` as the root router and `.ptsip/profiles/index.json` for local Project Profile selection. The Task and runtime namespaces are reserved; runtime persistence details remain future work. A reserved or unavailable Task capability must fail closed for the dependent operation rather than causing an agent to invent a new Task Engine elsewhere in the repository.
 
 ## Project status
 
-PTSIP remains experimental. Tool `0.3.8a2` is the current namespace-stabilization prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a2.md`](releasenote/tool/0.3.8a2.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).
+PTSIP remains experimental. Tool `0.3.8a4` is the current Go-native developer automation and release-verification consolidation prerelease candidate; its publication boundary is tracked in [`releasenote/tool/0.3.8a4.md`](releasenote/tool/0.3.8a4.md). Historical Tool releases, including `0.3.8a1`, and Specification notes are preserved under [`releasenote/`](releasenote/).

{ptsip-0.3.8a2 → ptsip-0.3.8a4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "PTSIP"
-version = "0.3.8a2"
+version = "0.3.8a4"
 description = "Reference tooling for primary lifecycle ownership and responsibility isolation"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -45,8 +45,14 @@ ptsip-app = "ptsip.app.server:main"
 [tool.setuptools.packages.find]
 where = ["src"]
 include = ["ptsip*", "vpms*", "agent_contracts*"]
+exclude = ["tests*", "ptsip.profiles.history*"]
 
 [tool.setuptools.package-data]
+"ptsip.profiles" = ["index.yaml", "*.ptsip.yaml"]
+vpms = [
+  "contracts/*.json",
+  "contracts/schemas/*.json",
+]
 ptsip = [
   "specdata/*.json",
   "specdata/*.yaml",
@@ -69,6 +75,17 @@ agent_contracts = [
   "gates/*.yaml",
   "vocabulary/*.yaml",
   "bindings/*.yaml",
+  "index.json",
+  "contracts/current.json",
+  "conformance/current.json",
+  "promotion/current.json",
+  "promotion/index.json",
+  "promotion/specification-contract.json",
+  "canonicalization/*.json",
+  "digests/*.json",
+  "schemas/candidate-index.schema.json",
+  "schemas/candidate-group.schema.json",
+  "schemas/candidate-vectors.schema.json",
 ]
 
 [project.optional-dependencies]
@@ -80,3 +97,6 @@ dev = [
   "pytest>=8,<9",
   "setuptools>=77.0.3",
 ]
+
+[tool.setuptools.exclude-package-data]
+"ptsip.profiles" = ["history/*", "history/**"]

{ptsip-0.3.8a2 → ptsip-0.3.8a4}/registry/project-profile-contracts.yaml

@@ -1,6 +1,11 @@
 schema_version: ptsip-project-profile-contract-registry/v1
 authority: PTSIP_PROJECT_PROFILE_CONTRACT_IDENTITY
 current: pp.1.02
+profile_source:
+  root: src/ptsip/profiles
+  catalog: src/ptsip/profiles/index.yaml
+  history_root: src/ptsip/profiles/history
+  history_distribution: SOURCE_ONLY
 contracts:
   - version: pp.0.00
     lifecycle: LEGACY_COMPATIBILITY_ONLY
@@ -15,7 +20,7 @@ contracts:
       - ANALYZE
       - CREATE_TARGET
     schema: schemas/ptsip-profile-pp-1.01.schema.json
-    baseline: profiles/history/pp.1.01
+    baseline: src/ptsip/profiles/history/pp.1.01
   - version: pp.1.02
     lifecycle: CURRENT
     operations:
@@ -24,7 +29,7 @@ contracts:
       - ANALYZE
       - CREATE_TARGET
     schema: schemas/ptsip-profile-pp-1.02.schema.json
-    baseline: profiles/history/pp.1.02
+    baseline: src/ptsip/profiles/history/pp.1.02
 transitions:
   - from: pp.1.01
     to: pp.1.02

{ptsip-0.3.8a2 → ptsip-0.3.8a4}/setup.py

@@ -9,8 +9,8 @@ from setuptools.command.build_py import build_py as _build_py
 
 
 ROOT = Path(__file__).resolve().parent
-CANONICAL_SUPPORT_POLICY = ROOT / "docs" / "Support_policy" / "policy"
-CANONICAL_PUBLIC_PROFILES = ROOT / "profiles"
+CANONICAL_SUPPORT_POLICY = ROOT / "src" / "policy"
+CANONICAL_PUBLIC_PROFILES = ROOT / "src" / "ptsip" / "profiles"
 CANONICAL_PUBLIC_PROFILE_CATALOG = CANONICAL_PUBLIC_PROFILES / "index.yaml"
 CANONICAL_PP_CONTRACT_REGISTRY = ROOT / "registry" / "project-profile-contracts.yaml"
 EMBEDDED_PP_CONTRACT_REGISTRY = (
@@ -40,11 +40,14 @@ def _project_support_policy(build_lib: Path) -> None:
     policy_target.mkdir(parents=True, exist_ok=True)
     copy2(source / "index.yaml", policy_target / "index.yaml")
 
-    sfp_files = sorted(source.glob("SFP-*.yaml"))
+    sfp_files = sorted(source.rglob("SFP-*.yaml"))
     if not sfp_files:
         raise RuntimeError("canonical Support Policy source contains no SFP records")
     for path in sfp_files:
-        copy2(path, policy_target / path.name)
+        relative = path.relative_to(source)
+        destination = policy_target / relative
+        destination.parent.mkdir(parents=True, exist_ok=True)
+        copy2(path, destination)
 
     copytree(source / "schemas", target / "schemas")
     copytree(source / "registries", target / "registries")
@@ -52,8 +55,8 @@ def _project_support_policy(build_lib: Path) -> None:
 
 def _registered_public_profile_resources() -> tuple[str, ...]:
     catalog = _load_yaml(CANONICAL_PUBLIC_PROFILE_CATALOG)
-    if catalog.get("root") != "profiles":
-        raise RuntimeError("public Profile catalog root must be 'profiles'")
+    if catalog.get("root") != "src/ptsip/profiles":
+        raise RuntimeError("public Profile catalog root must be 'src/ptsip/profiles'")
 
     profiles = catalog.get("profiles")
     if not isinstance(profiles, list) or not profiles:
@@ -115,7 +118,7 @@ def _registered_profile_baselines() -> tuple[tuple[str, Path], ...]:
             continue
         if not isinstance(version, str) or not isinstance(baseline, str):
             raise RuntimeError("Project Profile baseline binding is invalid")
-        expected = f"profiles/history/{version}"
+        expected = f"src/ptsip/profiles/history/{version}"
         if baseline != expected:
             raise RuntimeError(
                 f"Project Profile baseline {baseline!r} must equal {expected!r}"
@@ -123,38 +126,48 @@ def _registered_profile_baselines() -> tuple[tuple[str, Path], ...]:
         source = ROOT / baseline
         if not source.is_dir():
             raise RuntimeError(f"registered Project Profile baseline is missing: {baseline}")
+        if not any(source.glob("*.ptsip.yaml")):
+            raise RuntimeError(f"registered Project Profile baseline is empty: {baseline}")
         baselines.append((version, source))
 
     current_baseline = current_matches[0].get("baseline")
-    if current_baseline != f"profiles/history/{current}":
+    if current_baseline != f"src/ptsip/profiles/history/{current}":
         raise RuntimeError("current Project Profile contract must bind its generation baseline")
     return tuple(baselines)
 
 
 def _project_public_profiles(build_lib: Path) -> None:
     resources = _registered_public_profile_resources()
-    baselines = _registered_profile_baselines()
+    _registered_profile_baselines()
 
     target = build_lib / "ptsip" / "profiles"
-    if target.exists():
-        rmtree(target)
     target.mkdir(parents=True, exist_ok=True)
+    # Preserve modules copied by build_py. History is source-only, including
+    # stale output left by an earlier build that shipped historical baselines.
+    history_target = target / "history"
+    if history_target.exists():
+        if not history_target.resolve().is_relative_to(build_lib.resolve()):
+            raise RuntimeError("historical build output escapes build directory")
+        rmtree(history_target)
+    for name in (
+        "profile_identity", "profile_metadata", "profile_compatibility",
+        "local_profile_catalog", "project_profile_contracts",
+    ):
+        retired = target.parent / f"{name}.py"
+        if retired.exists():
+            if not retired.resolve().is_relative_to(build_lib.resolve()):
+                raise RuntimeError("retired profile output escapes build directory")
+            retired.unlink()
+    for stale in target.glob("*.ptsip.yaml"):
+        if stale.name not in resources:
+            if not stale.resolve().is_relative_to(build_lib.resolve()):
+                raise RuntimeError("stale profile output escapes build directory")
+            stale.unlink()
 
     copy2(CANONICAL_PUBLIC_PROFILE_CATALOG, target / "index.yaml")
     for resource in resources:
         copy2(CANONICAL_PUBLIC_PROFILES / resource, target / resource)
 
-    for version, source in baselines:
-        history_target = target / "history" / version
-        history_target.mkdir(parents=True, exist_ok=True)
-        baseline_resources = sorted(source.glob("*.ptsip.yaml"))
-        if not baseline_resources:
-            raise RuntimeError(
-                f"registered Project Profile baseline contains no profiles: {source}"
-            )
-        for path in baseline_resources:
-            copy2(path, history_target / path.name)
-
     specdata_target = build_lib / "ptsip" / "specdata"
     specdata_target.mkdir(parents=True, exist_ok=True)
     copy2(