@mriekki/project-forge 2.2.0 → 4.0.0

package/assets/generated/deployment/docs/DEVELOPER_ENVIRONMENTS.md

@@ -13,7 +13,7 @@ The happy path intentionally hides Bootstrap/package/control-plane plumbing. Dev
 The normal progression is:
 
 ```text
-generated POC repository
+generated Project repository
 → clone/open workspace
 → /setup
 → LOCAL READY
@@ -42,7 +42,7 @@ The normal conversational entry point is:
 
 `/setup` explains the current state/options and invokes the correct repository-local setup launcher. Direct script invocation remains the non-AI/automation fallback.
 
-The first local success target is `LOCAL WORKSPACE READY`. Remote access must not block it unless the POC explicitly requires a remote dependency for local development.
+The first local success target is `LOCAL WORKSPACE READY`. Remote access must not block it unless the Project explicitly requires a remote dependency for local development.
 
 ## Progress and next action
 
@@ -156,11 +156,11 @@ A changed previously pinned host key remains a blocker and requires explicit tru
 
 ## Docker and host preparation
 
-Docker is a workstation/target capability, not something every POC should reinstall.
+Docker is a workstation/target capability, not something every Project should reinstall.
 
 ### Developer workstation
 
-The first POC on a computer may install/verify required local tools and Docker through the generated setup contract. Later POCs reuse the ready workstation.
+The first Project on a computer may install/verify required local tools and Docker through the generated setup contract. Later Projects reuse the ready workstation.
 
 ### Remote Ubuntu target
 
@@ -209,17 +209,17 @@ A credential needed to acquire a private image is entered only through the local
 
 If the exact immutable image is already cached locally, registry authentication is not required merely to transfer it to the remote target.
 
-## POC environment model
+## Project environment model
 
-![POC environment model](images/poc-environment-model.svg)
+![Project environment model](images/project-environment-model.svg)
 
-The POC owns project-specific facts such as environment identities/roles, placement, target binding, application image, runtime/health contract, persistence, routes/exposure, and Production classification/authorization.
+The Project owns project-specific facts such as environment identities/roles, placement, target binding, application image, runtime/health contract, persistence, routes/exposure, and Production classification/authorization.
 
-The reusable workstation/target layer owns machine mechanics. A POC references targets; it does not own or duplicate a developer's private credentials.
+The reusable workstation/target layer owns machine mechanics. A Project references targets; it does not own or duplicate a developer's private credentials.
 
 ## New workstation
 
-A developer normally starts from any generated POC:
+A developer normally starts from any generated Project:
 
 ```text
 clone repository
@@ -233,7 +233,7 @@ When GitHub is reachable, personal profile sync supplies portable target definit
 
 ## New remote box
 
-Adding a new remote target is a workstation-driven onboarding operation, not a POC implementation step:
+Adding a new remote target is a workstation-driven onboarding operation, not a Project implementation step:
 
 ```text
 add/import portable target definition
@@ -243,7 +243,7 @@ add/import portable target definition
 → TARGET READY
 ```
 
-Once ready, multiple POCs can bind logical environments to that target without repeating host bootstrap.
+Once ready, multiple Projects can bind logical environments to that target without repeating host bootstrap.
 
 ## Portable export/import fallback
 

package/assets/generated/deployment/docs/ENVIRONMENT_PROOF.md

@@ -1,6 +1,6 @@
 # Environment Proof Deployment
 
-A Project Forge environment proof verifies that one developer workstation can exercise the real remote deployment path for one exact named logical environment before the POC application exists or before its first real deployment.
+A Project Forge environment proof verifies that one developer workstation can exercise the real remote deployment path for one exact named logical environment before the Project application exists or before its first real deployment.
 
 It is intentionally **not** the project application.
 
@@ -84,7 +84,7 @@ The proof attempts cleanup even when deployment raises after mutation begins.
 
 Successful completion requires terminal cleanup evidence (`removed` or already `absent`) for the reserved probe runtime. If deployment succeeds but cleanup cannot be verified, the command fails rather than reporting a clean proof.
 
-The probe must not delete another POC, another application, another logical environment, or shared host platform state.
+The probe must not delete another Project, another application, another logical environment, or shared host platform state.
 
 ## Relationship to `/setup` and `/deploy`
 

package/assets/generated/deployment/docs/WORKSPACE_INSTANCES.md

@@ -63,7 +63,7 @@ Local mutable application data is not synchronized between workstations by Proje
 
 ## Setup on another workstation
 
-The normal flow for an existing generated POC is:
+The normal flow for an existing generated Project is:
 
 ```text
 clone repository

package/assets/generated/deployment/docs/images/developer-environment-journey.svg

@@ -1,6 +1,6 @@
 <svg xmlns="http://www.w3.org/2000/svg" width="1200" height="520" viewBox="0 0 1200 520" role="img" aria-labelledby="title desc">
   <title id="title">Project Forge developer environment journey</title>
-  <desc id="desc">Generated POC repository progresses through clone and setup to local ready, then optionally to staging ready and production ready.</desc>
+  <desc id="desc">Generated Project repository progresses through clone and setup to local ready, then optionally to staging ready and production ready.</desc>
   <defs>
     <linearGradient id="bg" x1="0" y1="0" x2="1" y2="1">
       <stop offset="0" stop-color="#0b1220"/>
@@ -20,7 +20,7 @@
   <g filter="url(#shadow)" font-family="Inter,Segoe UI,Arial,sans-serif">
     <rect x="70" y="180" width="205" height="128" rx="18" fill="#1e2a40" stroke="#405274" stroke-width="2"/>
     <text x="172" y="222" text-anchor="middle" font-size="15" font-weight="700" fill="#91a4c4">PROJECT</text>
-    <text x="172" y="254" text-anchor="middle" font-size="22" font-weight="700" fill="#ffffff">Generated POC</text>
+    <text x="172" y="254" text-anchor="middle" font-size="22" font-weight="700" fill="#ffffff">Generated Project</text>
     <text x="172" y="282" text-anchor="middle" font-size="15" fill="#b8c5d8">clone + open workspace</text>
 
     <rect x="360" y="180" width="205" height="128" rx="18" fill="#1f3440" stroke="#3b7584" stroke-width="2"/>

package/assets/generated/deployment/docs/images/{poc-environment-model.svg → project-environment-model.svg}

@@ -1,6 +1,6 @@
 <svg xmlns="http://www.w3.org/2000/svg" width="1200" height="720" viewBox="0 0 1200 720" role="img" aria-labelledby="title desc">
   <title id="title">Project Forge environment model</title>
-  <desc id="desc">A POC uses local workstation runtime and optional remote logical staging and production environments bound to reusable remote targets and shared host platform infrastructure.</desc>
+  <desc id="desc">A Project uses local workstation runtime and optional remote logical staging and production environments bound to reusable remote targets and shared host platform infrastructure.</desc>
   <defs>
     <linearGradient id="bg" x1="0" y1="0" x2="1" y2="1">
       <stop offset="0" stop-color="#0b1220"/>
@@ -14,12 +14,12 @@
     </marker>
   </defs>
   <rect width="1200" height="720" rx="24" fill="url(#bg)"/>
-  <text x="70" y="70" font-family="Inter,Segoe UI,Arial,sans-serif" font-size="30" font-weight="700" fill="#f7f9fc">POC Environment Model</text>
-  <text x="70" y="102" font-family="Inter,Segoe UI,Arial,sans-serif" font-size="17" fill="#aebbd0">The POC owns application/environment facts; reusable workstation and target layers own machine mechanics.</text>
+  <text x="70" y="70" font-family="Inter,Segoe UI,Arial,sans-serif" font-size="30" font-weight="700" fill="#f7f9fc">Project Environment Model</text>
+  <text x="70" y="102" font-family="Inter,Segoe UI,Arial,sans-serif" font-size="17" fill="#aebbd0">The Project owns application/environment facts; reusable workstation and target layers own machine mechanics.</text>
 
   <g filter="url(#shadow)" font-family="Inter,Segoe UI,Arial,sans-serif">
     <rect x="390" y="135" width="420" height="106" rx="20" fill="#25294a" stroke="#7277c9" stroke-width="2"/>
-    <text x="600" y="176" text-anchor="middle" font-size="15" font-weight="700" fill="#aaaef1">GENERATED POC</text>
+    <text x="600" y="176" text-anchor="middle" font-size="15" font-weight="700" fill="#aaaef1">GENERATED Project</text>
     <text x="600" y="209" text-anchor="middle" font-size="21" font-weight="700" fill="#ffffff">Environment bindings + app runtime facts</text>
 
     <rect x="95" y="330" width="300" height="190" rx="20" fill="#173c35" stroke="#3a9d82" stroke-width="2"/>

package/assets/generated/deployment/src/project_forge_deployment/cli.py

@@ -283,7 +283,7 @@ def build_parser() -> argparse.ArgumentParser:
     route_inventory_parser.add_argument("--json", action="store_true")
 
     route_register = route_sub.add_parser(
-        "register", help="Create or update one POC/environment-owned Caddy + mDNS route"
+        "register", help="Create or update one Project/environment-owned Caddy + mDNS route"
     )
     route_register.add_argument("name")
     route_register.add_argument("--owner-repo", required=True)

package/assets/generated/deployment/src/project_forge_deployment/entrypoint.py

@@ -33,5 +33,5 @@ def main(argv: list[str] | None = None) -> int:
         print("Command group: local  Loopback-only workstation application runtime")
         print("Command group: registry  Read-only exact-image registry access verification")
         print("Command group: sqlite  SQLite persistence import/backup/migration/rollback checks")
-        print("Command group: tear-down  Scoped destructive POC environment/local cleanup")
+        print("Command group: tear-down  Scoped destructive Project environment/local cleanup")
     return core_main(args)

package/assets/generated/deployment/src/project_forge_deployment/environment_probe.py

@@ -14,7 +14,7 @@ from .app_runtime_workstation import apply_app_deploy_from_workstation
 from .box_platform import platform_status
 from .errors import DeploymentKitError
 from .registry_access import normalize_registry_image
-from .teardown import tear_down_poc
+from .teardown import tear_down_project
 
 ENVIRONMENT_PROOF_WRITE_PHRASE = "[ENVIRONMENT PROOF WRITE]"
 PRODUCTION_ENVIRONMENT_PROOF_WRITE_PHRASE = "[PRODUCTION ENVIRONMENT PROOF]"
@@ -171,7 +171,7 @@ def run_environment_proof(plan: dict[str, Any]) -> dict[str, Any]:
         deploy_error = error
     finally:
         try:
-            cleanup = tear_down_poc(
+            cleanup = tear_down_project(
                 {
                     "ownerRepo": plan["ownerRepo"],
                     "appSlug": plan["probeAppSlug"],

package/assets/generated/deployment/src/project_forge_deployment/route_registry.py

@@ -270,7 +270,7 @@ def plan_route_registration(
         owner_fields = ("ownerRepo", "environment", "appSlug")
         if any(existing[field] != spec[field] for field in owner_fields):
             raise DeploymentKitError(
-                f"Route ID {spec['routeId']} is already owned by another POC/environment; refusing takeover."
+                f"Route ID {spec['routeId']} is already owned by another Project/environment; refusing takeover."
             )
     requested = set(spec["hostnames"])
     for route in inventory["managedRoutes"]:
@@ -312,7 +312,7 @@ def plan_route_removal(
     if existing is None:
         raise DeploymentKitError(f"Managed route does not exist: {route_id}")
     if existing["ownerRepo"] != owner_repo or existing["environment"] != environment or existing["appSlug"] != app_slug:
-        raise DeploymentKitError("Route removal ownership does not match the registered POC/environment.")
+        raise DeploymentKitError("Route removal ownership does not match the registered Project/environment.")
     return {
         "targetName": name,
         "action": "remove",

package/assets/generated/deployment/src/project_forge_deployment/teardown.py

@@ -15,7 +15,7 @@ from .route_registry import apply_route_change, plan_route_removal, route_invent
 from .ssh import ssh_args, verify_access
 from .teardown_remote import REMOTE_SCRIPT
 
-TEAR_DOWN_WRITE_PHRASE = "[POC TEAR DOWN]"
+TEAR_DOWN_WRITE_PHRASE = "[PROJECT TEAR DOWN]"
 PRODUCTION_DATA_DELETE_PHRASE = "[PRODUCTION DATA DELETE]"
 RESERVED_SCOPES = ("local", "all")
 
@@ -167,13 +167,13 @@ def _tear_down_remote_environment(
     stderr = completed.stderr.decode("utf-8", errors="replace").strip()
     if completed.returncode != 0:
         raise DeploymentKitError(
-            "Remote POC tear-down failed: " + (stderr or stdout or f"exit {completed.returncode}")
+            "Remote Project tear-down failed: " + (stderr or stdout or f"exit {completed.returncode}")
         )
     parts = stdout.split("\t")
     if len(parts) not in {4, 5} or parts[0] != "TEAR_DOWN" or parts[1] not in {"absent", "removed"}:
-        raise DeploymentKitError("Remote POC tear-down returned malformed evidence.")
+        raise DeploymentKitError("Remote Project tear-down returned malformed evidence.")
     if parts[2] != app_slug or parts[3] != environment:
-        raise DeploymentKitError("Remote POC tear-down returned mismatched app/environment evidence.")
+        raise DeploymentKitError("Remote Project tear-down returned mismatched app/environment evidence.")
     result: dict[str, Any] = {"state": parts[1], "mutated": parts[1] == "removed"}
     if len(parts) == 5:
         result["containerName"] = parts[4]
@@ -219,7 +219,7 @@ def tear_down_workstation_package(package: str) -> dict[str, Any]:
         removed = _run_local([docker, "rm", "-f", "-v", *containers])
         if removed.returncode != 0:
             raise DeploymentKitError(
-                "Local POC container removal failed: " + (removed.stderr or removed.stdout).strip()
+                "Local Project container removal failed: " + (removed.stderr or removed.stdout).strip()
             )
 
     images_result = _run_local([docker, "images", "--format", "{{.Repository}}:{{.Tag}}"])
@@ -238,7 +238,7 @@ def tear_down_workstation_package(package: str) -> dict[str, Any]:
         removed = _run_local([docker, "image", "rm", "-f", *image_refs])
         if removed.returncode != 0:
             raise DeploymentKitError(
-                "Local POC image removal failed: " + (removed.stderr or removed.stdout).strip()
+                "Local Project image removal failed: " + (removed.stderr or removed.stdout).strip()
             )
     return {
         "state": "removed" if containers or image_refs else "absent",
@@ -248,7 +248,7 @@ def tear_down_workstation_package(package: str) -> dict[str, Any]:
     }
 
 
-def tear_down_poc(spec: dict[str, Any]) -> dict[str, Any]:
+def tear_down_project(spec: dict[str, Any]) -> dict[str, Any]:
     normalized = normalize_teardown_spec(
         owner_repo=spec.get("ownerRepo"),
         app_slug=spec.get("appSlug"),

package/assets/generated/deployment/src/project_forge_deployment/teardown_cli.py

@@ -1,4 +1,4 @@
-"""CLI for scoped destructive POC tear-down."""
+"""CLI for scoped destructive Project tear-down."""
 
 from __future__ import annotations
 
@@ -12,7 +12,7 @@ from .teardown import (
     normalize_teardown_spec,
     parse_environment_targets,
     render_teardown_summary,
-    tear_down_poc,
+    tear_down_project,
 )
 
 
@@ -83,7 +83,7 @@ def _preview(spec: dict[str, object]) -> dict[str, object]:
         "deletesPersistentData": bool(spec["environmentTargets"]),
         "deletesProductionData": production,
         "preservesSharedPlatform": True,
-        "preservesUnrelatedPocs": True,
+        "preservesUnrelatedProjects": True,
         "deletesGhcrPackage": False,
         "requiredAuthorization": TEAR_DOWN_WRITE_PHRASE,
         "requiredProductionDataAuthorization": PRODUCTION_DATA_DELETE_PHRASE if production else None,
@@ -111,7 +111,7 @@ def main(argv: list[str] | None = None) -> int:
             and args.production_data_authorization != PRODUCTION_DATA_DELETE_PHRASE
         )
         if missing_general or missing_production:
-            print("POC TEAR-DOWN PREVIEW")
+            print("PROJECT TEAR-DOWN PREVIEW")
             print(render_teardown_summary(preview))
             if missing_general:
                 print(
@@ -126,8 +126,8 @@ def main(argv: list[str] | None = None) -> int:
                 )
             return 2
 
-        result = tear_down_poc(spec)
-        print("POC TEAR-DOWN COMPLETE")
+        result = tear_down_project(spec)
+        print("PROJECT TEAR-DOWN COMPLETE")
         print(render_teardown_summary(result))
         return 0
     except DeploymentKitError as exc:

package/assets/generated/deployment/src/project_forge_deployment/teardown_remote.py

@@ -1,4 +1,4 @@
-"""Remote destructive tear-down for one Kit-managed POC environment."""
+"""Remote destructive tear-down for one Kit-managed Project environment."""
 
 REMOTE_SCRIPT = r'''#!/usr/bin/env bash
 set -Eeuo pipefail
@@ -37,7 +37,7 @@ if [[ ! -e "$ROOT" ]]; then
 fi
 
 [[ -d "$ROOT" && ! -L "$ROOT" ]] || {
-    echo "POC environment root is not a safe managed directory: $ROOT" >&2
+    echo "Project environment root is not a safe managed directory: $ROOT" >&2
     exit 21
 }
 
@@ -46,16 +46,16 @@ HAS_PERSISTENCE=false
 [[ -f "$STATE" && ! -L "$STATE" ]] && HAS_STATE=true
 [[ -f "$PERSISTENCE" && ! -L "$PERSISTENCE" ]] && HAS_PERSISTENCE=true
 [[ "$HAS_STATE" == true || "$HAS_PERSISTENCE" == true ]] || {
-    echo "POC environment root has no managed ownership marker: $ROOT" >&2
+    echo "Project environment root has no managed ownership marker: $ROOT" >&2
     exit 21
 }
 
 if [[ "$HAS_STATE" == true ]] && ! assert_owned_marker "$STATE"; then
-    echo "POC deployment ownership mismatch for $ROOT" >&2
+    echo "Project deployment ownership mismatch for $ROOT" >&2
     exit 22
 fi
 if [[ "$HAS_PERSISTENCE" == true ]] && ! assert_owned_marker "$PERSISTENCE"; then
-    echo "POC persistence ownership mismatch for $ROOT" >&2
+    echo "Project persistence ownership mismatch for $ROOT" >&2
     exit 22
 fi
 
@@ -87,7 +87,7 @@ if [[ "$HAS_STATE" == true ]]; then
     fi
 fi
 
-# The verified environment root is owned by this POC/environment. Tear-down
+# The verified environment root is owned by this Project/environment. Tear-down
 # removes releases, evidence, persistent data, and backups together.
 rm -rf --one-file-system -- "$ROOT"
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mriekki/project-forge",
-  "version": "2.2.0",
+  "version": "4.0.0",
   "description": "Public consumer distribution and updater for Project Forge engineering assets.",
   "type": "module",
   "bin": {

package/assets/generated/core/core/agents/coach.agent.md

@@ -1,69 +0,0 @@
----
-name: Coach
-description: Optional guided engineering-learning agent using actual repository context for concepts, code walkthroughs, debugging, coding/SQL/system-design drills, interviews, diagrams, and resources.
-user-invocable: true
-disable-model-invocation: true
----
-
-# Coach
-
-You are the optional engineering-learning perspective.
-
-Coaching is never required to start, continue, review, accept, deliver, merge, or complete engineering work.
-
-## Core behavior
-
-- Do not edit production code or implement fixes for the developer.
-- Do not invoke subagents.
-- Do not silently broaden product scope.
-- Do not pin/request/switch to a premium model automatically.
-- Read minimum relevant context.
-- Use actual repository code, requirements, tests, diffs, incidents, and decisions when useful.
-- Ask one material question at a time.
-- Continue automatically until stop/natural completion.
-- Adapt difficulty to demonstrated understanding.
-- Challenge shallow explanations.
-- Distinguish actual implementation/understanding from AI-generated work or study.
-
-## Depth and levels
-
-Depth: Light, Focused, Deep, Broad, or Coach recommends.
-
-Levels:
-
-```text
-L1 Recognize
-L2 Explain
-L3 Trace
-L4 Apply / Debug
-L5 Defend / Design
-L6 Interview Ready
-```
-
-Do not inflate mastery.
-
-## Modes
-
-Support concept learning, real-code walkthroughs, debugging, coding/DSA, SQL/database, design defense, system design, interview drills, gap assessment, learning paths, diagrams, and optional external resources.
-
-For a structured walkthrough of a changed implementation across a Git/PR/commit change set, route to `/code-walkthrough` when available. Use Coach directly for ad-hoc code explanation or deeper concept exploration.
-
-Use installed learning assets when present; otherwise coach directly from the repository/context.
-
-## Adaptive questioning
-
-Weak answer → teach/simplify/own-words explanation.
-
-Solid answer → application/edge case.
-
-Strong answer → tradeoff/debug/design.
-
-Very strong answer → scale/change assumptions/interviewer pressure.
-
-## Resources and progress
-
-Prefer official documentation and a small number of current high-quality tutorials/resources. External material is optional.
-
-Only update an optional learning-progress tracker with explicit human choice.
-
-Never turn study or personal-project understanding into false claims of professional experience.

package/assets/generated/core/core/skills/core-sync/SKILL.md

@@ -1,184 +0,0 @@
----
-name: core-sync
-description: Direct Core-to-consumer synchronization for component-only consumers; package-managed consumers are routed to /project-forge-update so umbrella and component baselines remain coherent.
-argument-hint: "[optional local Core path]"
-user-invocable: true
-disable-model-invocation: true
----
-
-# Core Sync
-
-`/core-sync` is the direct component synchronization path for consumers that are managed directly by `CORE_BASELINE.json` **without** an umbrella `PROJECT_FORGE_BASELINE.json`.
-
-For package-managed consumers, `/project-forge-update` is authoritative.
-
-Invocation starts read-only. Direct component synchronization must never make a package-managed consumer disagree with its recorded Project Forge package provenance.
-
-## 1. Classify the consumer before doing anything else
-
-From the consumer repository read, when present:
-
-- `PROJECT_FORGE_BASELINE.json`;
-- `CORE_BASELINE.json`;
-- `.github/project-forge-workspace.json`;
-- `.github/project-forge-core-sync.json`;
-- current Git status, branch, remotes, and default branch when observable.
-
-### Package-managed consumer
-
-If `PROJECT_FORGE_BASELINE.json` exists:
-
-```text
-PACKAGE-MANAGED PROJECT FORGE CONSUMER
-Direct Core sync: NOT PERMITTED
-Next: /project-forge-update
-```
-
-Stop before refreshing a Core checkout, running `tools/package/sync.py`, creating a sync branch, or sending a remote `[sync-core]` request.
-
-The umbrella package updates Core and Deployment components together and refreshes `PROJECT_FORGE_BASELINE.json`, `CORE_BASELINE.json`, and `DEPLOYMENT_BASELINE.json` coherently. A Core-only sync would bypass that contract.
-
-### Component-only Core consumer
-
-If `PROJECT_FORGE_BASELINE.json` is absent and a valid `CORE_BASELINE.json` exists, continue with the component-managed path below.
-
-If neither baseline exists, report `CORE SYNC BLOCKED`; do not invent provenance or initialize a consumer implicitly.
-
-## 2. Establish the component-only Core baseline
-
-Run the repository-local integrity check before planning an update:
-
-```text
-python tools/project-forge-core/check-core-baseline.py --root .
-```
-
-Stop if the managed overlay has unexplained local drift, missing managed files, or invalid baseline metadata.
-
-Resolve from `CORE_BASELINE.json`:
-
-- canonical Core repository;
-- currently accepted Core commit/version;
-- distribution name;
-- managed-path ownership/hashes.
-
-## 3. Resolve the Core source safely
-
-Check local candidates in this order:
-
-1. an explicit Core path supplied by the human;
-2. an already-open workspace folder that unambiguously resolves to the recorded Core repository;
-3. the sibling checkout derived from the Core repository name, normally `../project-forge-core`.
-
-Do not broadly scan the filesystem. A local Core checkout is an optimization, not a prerequisite.
-
-A local candidate is usable only when it is the recorded Git repository and its state can be inspected safely.
-
-If no usable local Core checkout exists, use the configured remote provider from `.github/project-forge-core-sync.json` when available. Do not ask the developer to clone Core merely to satisfy `/core-sync`.
-
-## 4. Classify a local Core checkout
-
-Before modifying a local Core checkout inspect:
-
-```text
-git -C <core-path> status --short --branch
-git -C <core-path> branch --show-current
-git -C <core-path> remote -v
-git -C <core-path> branch -vv
-```
-
-It may be refreshed automatically only when clean, on its normal accepted/default branch, backed by an unambiguous upstream, and fast-forward-safe.
-
-Never auto-stash, merge, rebase, reset, clean, force-update, or discard Core work.
-
-If the checkout is dirty, ahead, diverged, intentionally pinned, or ambiguous, preserve it unchanged and prefer the configured remote provider when available.
-
-## 5. Present one bounded component-sync choice
-
-Use the host-native **single-select structured choice UI** when available because exactly one next action is authorized. In VS Code use the native question surface such as `vscode_askQuestions`. Preserve the consequence labels and show the recommended choice. Use a numbered text list only when structured choice UI is unavailable.
-
-For a safe local source, show the evidence:
-
-```text
-CORE SYNC READY
-
-Consumer baseline: <commit/version>
-Source: LOCAL <core-path>
-Distribution: <distribution>
-```
-
-Then offer:
-
-- `Sync the component-only Core baseline` `[GIT + FILE WRITE]` — `RECOMMENDED`
-- `Keep inspecting only` `[READ ONLY]`
-- `Stop` `[NO ACTION]`
-
-For a configured remote source, show:
-
-```text
-CORE SYNC READY
-
-Consumer baseline: <commit/version>
-Source: REMOTE PROVIDER
-Provider: <provider repository>
-```
-
-Then offer:
-
-- `Request remote Core sync` `[REMOTE WRITE]` — `RECOMMENDED`
-- `Keep inspecting only` `[READ ONLY]`
-- `Stop` `[NO ACTION]`
-
-The selected choice does not authorize merge, release publication, or deployment.
-
-## 6. Local component path
-
-After `Sync the component-only Core baseline` is selected:
-
-1. Refresh Core remote state.
-2. Reclassify the accepted/default Core branch.
-3. Fast-forward it only when safe.
-4. Run canonical Core sync preview using the distribution recorded by the baseline.
-5. Stop on `LOCAL_DRIFT`, `CONFLICT`, `LOCAL_MISSING`, `UNTRACKED_CONFLICT`, or an unaccepted `RETIRED_PATH`.
-6. If the consumer is on its default branch, create/switch to a short-lived branch such as `chore/sync-core-<version-or-short-sha>`.
-7. Apply only safe Core additions/updates and refresh `CORE_BASELINE.json` using canonical `tools/package/sync.py`.
-
-Do not manually copy managed files as a substitute for the canonical tool.
-
-## 7. Remote component path
-
-Remote orchestration is consumer configuration. Read `.github/project-forge-core-sync.json` and require its configured provider contract, for example `github-issue-control-plane` with an owner/repository title template and an empty body.
-
-Create exactly the configured request. Do not put product requirements, baseline JSON, source code, secrets, or other private consumer details into a public request.
-
-The provider is expected to validate target authorization, obtain its own short-lived credentials, run canonical Core sync, refuse unsafe drift/conflicts, publish a short-lived consumer branch/PR, and observe consumer CI.
-
-If the provider cannot satisfy that contract, report `REMOTE SYNC UNAVAILABLE`; do not silently clone Core or invent another synchronization mechanism.
-
-## 8. Verification
-
-For a local apply run:
-
-```text
-python tools/project-forge-core/check-core-baseline.py --root .
-git status --short --branch
-git diff --stat
-git diff -- CORE_BASELINE.json
-```
-
-Confirm exact Core provenance, managed hashes, consumer-owned preservation, and intended branch scope. Present the meaningful diff and recommend `/deliver` after human acceptance.
-
-For a remote path, report the resulting PR and exact Core commit when observed. Merge remains the normal explicit final gate.
-
-## 9. Boundaries
-
-`/core-sync` never:
-
-- directly synchronizes Core when `PROJECT_FORGE_BASELINE.json` exists;
-- uses direct Core sync as a substitute for `/project-forge-update`;
-- modifies ambiguous local Core state;
-- treats managed consumer drift as disposable;
-- publishes Core or Project Forge package releases/tags;
-- merges the consumer sync PR;
-- deploys production.
-
-If reusable Core behavior itself is wrong, fix Core canonically through `/upstream-fix`; then adopt it through the update channel appropriate to the consumer's provenance model.