@mriekki/lean 0.1.0 → 0.2.0

package/assets/generated/ASSEMBLY.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
   "package": "@mriekki/lean",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "components": {
     "core": {
       "repository": "mriekki/lean-agentic-core",
-      "commit": "e2d64b10f1a30507471755339c20e8b58e62be16",
-      "version": "1.10.0",
+      "commit": "5b2f13bb188f74fa0d7b6b8d7985fe3abfc543f9",
+      "version": "1.11.0",
       "distribution": "greenfield-workspace",
       "files": [
         {
@@ -79,15 +79,20 @@
           "destination": ".github/skills/pull-latest/SKILL.md",
           "sha256": "d49321859fe37afeb5d9e0b39ceac3d8a6709f6e02efd19b6cac37842fe3aa37"
         },
+        {
+          "source": "core/skills/lean-update/SKILL.md",
+          "destination": ".github/skills/lean-update/SKILL.md",
+          "sha256": "b9534533c2b612f2787ce4b9d40494bd5a3554ccb646f500610fb899be8113d2"
+        },
         {
           "source": "core/skills/core-sync/SKILL.md",
           "destination": ".github/skills/core-sync/SKILL.md",
-          "sha256": "6b2393639f3cc0581bed0df8667fc67691ae915d137b9f070c60bbdb042148a6"
+          "sha256": "0c1bfbc7678f5ae3239dd2900a12e75584035a5338474181dbd81cb1a0813531"
         },
         {
           "source": "core/skills/upstream-fix/SKILL.md",
           "destination": ".github/skills/upstream-fix/SKILL.md",
-          "sha256": "26d979b8876db4031f7e95887ab16a7c530d1fcd60043410ed8d20c4ea5f5301"
+          "sha256": "d6b77eee298bf387e20156c6ff7b3904e3f925873699f7e1071515d9d69c2f03"
         },
         {
           "source": "core/skills/wait-what/SKILL.md",
@@ -102,7 +107,7 @@
         {
           "source": "core/skills/deploy/SKILL.md",
           "destination": ".github/skills/deploy/SKILL.md",
-          "sha256": "57fca71a95a32f4dd17ed3fba13b9b1ccbd644082de175622960d9c65aaa47a0"
+          "sha256": "e9dcf7232505d684c1d8f39b0937c5026223e745df023c84295457e22da1b52a"
         },
         {
           "source": "core/skills/tear-down/SKILL.md",
@@ -244,137 +249,137 @@
         {
           "source": "distribution/lean-poc-deploy.py",
           "destination": "tools/lean-deployment/lean-poc-deploy.py",
-          "sha256": "98e282d4f85999c3a37c47af6805cfa645f7de6e7e2e4a686e4d0012850805df"
+          "sha256": "4f300e1de447f6b8ecd57f561bdf000743baaa39051aa359f65d0a051be2e220"
         },
         {
           "source": "src/lean_poc_deployment/__init__.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/__init__.py",
-          "sha256": "9f84e6ff170f657459fc461833007f874c6fdd4f6c6d3964ee41d7ec3d0e33d0"
+          "sha256": "47695e1cc417117ee5d5e7b85d3301fd0dc99963eacfedbe499f3798d28dee72"
         },
         {
           "source": "src/lean_poc_deployment/__main__.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/__main__.py",
-          "sha256": "5791f61aa75f2048bb7ef968f382ca81b7c14520599f0d358113fde33392e7ee"
+          "sha256": "8742c1b766812edb07174a724d676ffeff58b71b3c192d35102a3e652e962946"
         },
         {
           "source": "src/lean_poc_deployment/app_cli.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/app_cli.py",
-          "sha256": "a70e0471a34a111eecf4c26c49a76273b53dd67351f9c57484bf58a7372baf4a"
+          "sha256": "29cf78cd27302341d5fe74877e6b4e211a465bb9991fc720585122f7d4b49190"
         },
         {
           "source": "src/lean_poc_deployment/app_runtime.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/app_runtime.py",
-          "sha256": "9cd033b0d483dabf28c9ff4289a0d7621e8e8355704c94221238fa33905b9ae4"
+          "sha256": "68c623735fc45b6d20cdfc5c110cfa41a4540f030da479d355b456a1e13a21a3"
         },
         {
           "source": "src/lean_poc_deployment/app_runtime_remote.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/app_runtime_remote.py",
-          "sha256": "7433314dedf08a189b7c672897a499367511778bedc0f1080ae6c72bb86f9867"
+          "sha256": "f3ccde6ed3c6e5fe185a9a0f032a5c924fa0906e3619e12d0ad6228c1210f8ec"
         },
         {
           "source": "src/lean_poc_deployment/box_platform.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/box_platform.py",
-          "sha256": "346f3f61252bc61f052ddc1865d6843a4ca512f6a5f67d80d0e13c7d878863ba"
+          "sha256": "163c022bbd8ecccadebbebdc8cef8e272fc95dd0dc3cdb35d4e6e10013c91040"
         },
         {
           "source": "src/lean_poc_deployment/box_platform_assets.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/box_platform_assets.py",
-          "sha256": "c2787fc800afec76183fbcb0bb27e96b016ea65b6a5fec62595eb68b01b90561"
+          "sha256": "07ef27a63ebff9fb2a810d0c40dd601e14f767c6f8faaedcedd54bb3b79ffef4"
         },
         {
           "source": "src/lean_poc_deployment/box_platform_remote.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/box_platform_remote.py",
-          "sha256": "1e5094c48ada1b92e19e94d2ad8140de54645da3ab32d3ae2a09478f459d2e7d"
+          "sha256": "1702614cada6f0829abe1d412d8a90f7452c96db2f2693631d20cdb08de29aaa"
         },
         {
           "source": "src/lean_poc_deployment/cli.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/cli.py",
-          "sha256": "d6da84777cdae2e55dd636adc3e90fc8cbc777a29dd5df85a936c1cbb2cf3f05"
+          "sha256": "a30230969a27ec0df67f311694c13c91520f11104ceae2906cc9f5f46e6f8b23"
         },
         {
           "source": "src/lean_poc_deployment/doctor.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/doctor.py",
-          "sha256": "1b86ee7df00b5e10c3859bc227562d14a954ebbe9f68fea12ff63f290e888926"
+          "sha256": "139914e437832fd8c5b8d2d8d6fc0ef8aa004862fde45989547e572c461f299d"
         },
         {
           "source": "src/lean_poc_deployment/entrypoint.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/entrypoint.py",
-          "sha256": "62112d18f265dea737748e61216c25f9c52a1174e0d4bd69d6afe09fa8097e26"
+          "sha256": "08a27a64680f7a72b68c6272f5185c7fdb23678efbda456fd0894272e2e6187e"
         },
         {
           "source": "src/lean_poc_deployment/errors.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/errors.py",
-          "sha256": "ecee46ca5746e5225a4cc30aa2cdc57a8746658d9b3ab45f7c9a775e24f9b5b6"
+          "sha256": "0bc20b1b739f999960422b7bd05249f4179f3612910ecbb6cf2805b5f4babd61"
         },
         {
           "source": "src/lean_poc_deployment/keys.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/keys.py",
-          "sha256": "91777f7c0716d44157320fcbadae1bd2c24d04caa1dce5c15c7fca91af3a2e02"
+          "sha256": "5a85bb6941957c45eb3c30ef1f350b669932287b9e2f4a23178260c72009e26c"
         },
         {
           "source": "src/lean_poc_deployment/profiles.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/profiles.py",
-          "sha256": "f9d1ae5e0690dc2e4e733153bb5f4427e53636a2c224a5e67c35493702733d7e"
+          "sha256": "9d73f86714db5c59a07354348e394647d62a3c31b173c4d3c4c4353872da908a"
         },
         {
           "source": "src/lean_poc_deployment/teardown.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/teardown.py",
-          "sha256": "041d93558ed69379429c193c5a058c2aa5ba8991c0a57ce3387b61c65fbd76a0"
+          "sha256": "edcf921aa92988176b756abf4bbc9b0b83ae1d855b6e8d487b67aaad7727cb55"
         },
         {
           "source": "src/lean_poc_deployment/teardown_cli.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/teardown_cli.py",
-          "sha256": "cae6721ad047822ac77942059bd4da3f34af382002eb284f144d4aae8470f69f"
+          "sha256": "ec1271db5f57135189892e87f2df3ffc5fcb6e763ff1eb9604bc4e50788c3325"
         },
         {
           "source": "src/lean_poc_deployment/teardown_remote.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/teardown_remote.py",
-          "sha256": "a3f30f66d1d7ad2d54ec9d2e55fe1cd4112f655e51ee0f4d24682ec3ed4cf9dd"
+          "sha256": "9745fd9f721eea2da8f5d32688cc6a293e46aa9f9e5c5825c6a08cacb1121fb1"
         },
         {
           "source": "src/lean_poc_deployment/route_registry.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/route_registry.py",
-          "sha256": "a3404ce7a4a84f2daa33f30eb09ffe19eaf19c72a44ae8a986d9b5ef0e7fc729"
+          "sha256": "8c19da6790fac66d0cb8fe099fb09c026966a6e5952df58bd936ce03a72f1928"
         },
         {
           "source": "src/lean_poc_deployment/route_registry_remote.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/route_registry_remote.py",
-          "sha256": "e7254f6949e3e234ed113eccec492976aacbbedaa5ea127ebdcebd9fdf12959b"
+          "sha256": "84c37f417ff21f05e7802acef33f4927c878e92f7ae791462eef77281f052bdf"
         },
         {
           "source": "src/lean_poc_deployment/security.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/security.py",
-          "sha256": "e18c93066132b176b95d91cd423cd6047648a492c8efc992d6ea2c9f633ad7b3"
+          "sha256": "f0946186e384794c81a78fbf50b6afdbbd79a0b22216034778fbb24d523696b6"
         },
         {
           "source": "src/lean_poc_deployment/sqlite_adapter.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/sqlite_adapter.py",
-          "sha256": "a9627729b66a50f743b05918da705a10f59efd519b5395c3f4ffdb25f7c54bb0"
+          "sha256": "b6f5fd33b776a1fb02d6b6a00fbab0b95827946e5fee51aafef9446fa084f42b"
         },
         {
           "source": "src/lean_poc_deployment/sqlite_adapter_remote.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/sqlite_adapter_remote.py",
-          "sha256": "5f24e730d76b357edd11f0bc98a8869fcb132cedde82374f4ae7690bba754b66"
+          "sha256": "77feaf6d60632375be4407145741244198f1836eff02e2d8c85f86c8d2c374e2"
         },
         {
           "source": "src/lean_poc_deployment/sqlite_cli.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/sqlite_cli.py",
-          "sha256": "83db4958fa84c2c52a5ebea242a0a7beb0222bc4ba8a03c32121ab8e7c9c8212"
+          "sha256": "0b68c0cd8c92a7e59071b6f922fe6bbf38d03276387856d1efa743118467bbca"
         },
         {
           "source": "src/lean_poc_deployment/sqlite_import_recovery.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/sqlite_import_recovery.py",
-          "sha256": "90524f94f46789786fb5d40fb7c402d54cfc8618f7bc1dd9a94605cabe4fb6fe"
+          "sha256": "8bba9aeb1ff2aca5360972a3f66e3dd8e3dc3a6484f5091af201f447454ab4f5"
         },
         {
           "source": "src/lean_poc_deployment/ssh.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/ssh.py",
-          "sha256": "42fe2ae7e57695b74b387cec33e413bfb61da46a18a92d6d457f70278e91a4bf"
+          "sha256": "9eb568ec75a288b1069e629c67d567d5bb0a7a2074563c70f49057326154f7d2"
         },
         {
           "source": "src/lean_poc_deployment/trust.py",
           "destination": "tools/lean-deployment/lean_poc_deployment/trust.py",
-          "sha256": "fdc6ddd7fca6f5ee310d6d50250d5b364fb4a0e92c71b6758e6b7f0045461645"
+          "sha256": "b143fa828c3a23df3909dacfd78ae56b9ec1159628eb45261d69c0aa6ddd1a7b"
         }
       ]
     }

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

@@ -1,6 +1,6 @@
 ---
 name: core-sync
-description: Guided Core-to-consumer synchronization that uses a safe local Core checkout when available and otherwise uses configured remote orchestration without requiring a Core clone.
+description: Compatibility Core-to-consumer synchronization for component-only consumers; package-managed consumers are routed to /lean-update so umbrella and component baselines remain coherent.
 argument-hint: "[optional local Core path]"
 user-invocable: true
 disable-model-invocation: true
@@ -8,55 +8,74 @@ disable-model-invocation: true
 
 # Core Sync
 
-`/core-sync` updates a consumer repository to a newer accepted Lean Agentic Core baseline while preserving consumer-owned content and the Human-in-the-Loop delivery boundary.
+`/core-sync` is the compatibility synchronization path for consumers that are managed directly by `CORE_BASELINE.json` **without** an umbrella `LEAN_BASELINE.json`.
 
-A local Core checkout is an optimization, not a prerequisite. Do not clone Core merely to satisfy `/core-sync`.
+For package-managed consumers, `/lean-update` is authoritative.
 
-Invocation starts read-only. One explicit sync choice may authorize the bounded mechanics needed for the selected local or remote path; merge/final acceptance remains separate.
+Invocation starts read-only. Direct component synchronization must never make a package-managed consumer disagree with its recorded Lean package provenance.
 
-## 1. Establish the consumer baseline
+## 1. Classify the consumer before doing anything else
 
-From the consumer repository, read:
+From the consumer repository read, when present:
 
-- `CORE_BASELINE.json`,
-- `.github/lean-workspace.json` when present,
-- `.github/lean-core-sync.json` when present,
+- `LEAN_BASELINE.json`;
+- `CORE_BASELINE.json`;
+- `.github/lean-workspace.json`;
+- `.github/lean-core-sync.json`;
 - current Git status, branch, remotes, and default branch when observable.
 
+### Package-managed consumer
+
+If `LEAN_BASELINE.json` exists:
+
+```text
+PACKAGE-MANAGED LEAN CONSUMER
+Direct Core sync: NOT PERMITTED
+Next: /lean-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 `LEAN_BASELINE.json`, `CORE_BASELINE.json`, and `DEPLOYMENT_BASELINE.json` coherently. A Core-only sync would bypass that contract.
+
+### Component-only Core consumer
+
+If `LEAN_BASELINE.json` is absent and a valid `CORE_BASELINE.json` exists, continue with the compatibility 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/lean-core/check-core-baseline.py --root .
 ```
 
-Stop if the current managed overlay already has unexplained local drift, missing managed files, or invalid baseline metadata. Do not treat consumer edits as disposable.
+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,
+- canonical Core repository;
+- currently accepted Core commit/version;
+- distribution name;
 - managed-path ownership/hashes.
 
-## 2. Resolve the Core source automatically
+## 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,
+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 `../lean-agentic-core`.
 
-Do not broadly scan the developer's filesystem.
-
-A local candidate is usable only when:
+Do not broadly scan the filesystem. A local Core checkout is an optimization, not a prerequisite.
 
-- it is a Git repository,
-- its configured remote resolves to the Core repository recorded in `CORE_BASELINE.json`,
-- its repository state can be inspected safely.
+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/lean-core-sync.json` when available. Do not ask the developer to clone Core just because the local candidate is absent.
+If no usable local Core checkout exists, use the configured remote provider from `.github/lean-core-sync.json` when available. Do not ask the developer to clone Core merely to satisfy `/core-sync`.
 
-## 3. Classify a local Core checkout
+## 4. Classify a local Core checkout
 
 Before modifying a local Core checkout inspect:
 
@@ -67,49 +86,35 @@ git -C <core-path> remote -v
 git -C <core-path> branch -vv
 ```
 
-A local Core checkout may be automatically refreshed only when all of these are true:
-
-- the worktree is clean,
-- no merge/rebase/cherry-pick is in progress,
-- the checkout is on its normal accepted/default branch,
-- an unambiguous upstream exists,
-- updating can be performed fast-forward-only.
+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 local Core checkout is dirty, ahead, diverged, on an intentional non-default ref, or otherwise ambiguous, preserve it unchanged. When a remote provider is configured, prefer the remote path for the consumer update. Otherwise stop with the observed local state and the missing capability; do not silently use an unaccepted local ref.
-
-## 4. Present one bounded sync choice
+If the checkout is dirty, ahead, diverged, intentionally pinned, or ambiguous, preserve it unchanged and prefer the configured remote provider when available.
 
-### Safe local Core available
+## 5. Present one bounded compatibility-sync choice
 
-Present:
+For a safe local source:
 
 ```text
-CORE SYNC READY
+CORE COMPATIBILITY SYNC READY
 
 Consumer baseline: <commit/version>
 Source: LOCAL <core-path>
-Local Core state: CURRENT | FAST-FORWARDABLE
 Distribution: <distribution>
 
-1. Sync to the accepted Core source [GIT + FILE WRITE] — recommended
+1. Sync the component-only Core baseline [GIT + FILE WRITE] — recommended
 2. Keep inspecting only [READ ONLY]
 3. Stop [NO ACTION]
 ```
 
-Choosing option 1 authorizes only the bounded local-sync mechanics described below: safe Core refresh if needed, consumer sync-branch setup, safe Core overlay application, and verification. It does not authorize `/deliver`, merge, release publication, or production deployment.
-
-### No safe local Core available, remote provider configured
-
-Present:
+For a configured remote source:
 
 ```text
-CORE SYNC READY
+CORE COMPATIBILITY SYNC READY
 
 Consumer baseline: <commit/version>
 Source: REMOTE PROVIDER
-Local Core: NOT REQUIRED
 Provider: <provider repository>
 
 1. Request remote Core sync [REMOTE WRITE] — recommended
@@ -117,70 +122,35 @@ Provider: <provider repository>
 3. Stop [NO ACTION]
 ```
 
-Choosing option 1 authorizes creation of exactly the configured remote sync request for this consumer. It does not authorize merging the resulting consumer PR.
+The selected choice does not authorize merge, release publication, or deployment.
 
-### Neither source is usable
+## 6. Local compatibility path
 
-Report `CORE SYNC BLOCKED` with the evidence. A missing local Core checkout by itself is not an error; the blocker is the absence of both a safe local source and a configured/usable remote provider.
+After local option 1 is selected:
 
-## 5. Local sync path
-
-After option 1 is selected:
-
-1. Refresh the local Core remote state.
+1. Refresh Core remote state.
 2. Reclassify the accepted/default Core branch.
-3. If behind and fast-forward-safe, update using the equivalent of:
-
-```text
-git -C <core-path> pull --ff-only
-```
-
-4. If Core is ahead, diverged, dirty, or otherwise unsafe after refresh, stop without changing the consumer and prefer the configured remote provider when available.
-5. Run a Core sync preview from the refreshed checkout using the distribution recorded by the consumer baseline.
-6. Stop without apply on any unsafe sync state, including `LOCAL_DRIFT`, `CONFLICT`, `LOCAL_MISSING`, `UNTRACKED_CONFLICT`, or an unaccepted `RETIRED_PATH`.
-7. If the consumer is on its default branch, create/switch to a repository-appropriate short-lived chore branch such as `chore/sync-core-<version-or-short-sha>`. This branch setup is routine inside the selected bounded sync action.
-8. Apply only the safe Core additions/updates and refresh `CORE_BASELINE.json` using Core's canonical `tools/package/sync.py` contract.
+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 individual managed files as a substitute for the canonical sync tool.
+Do not manually copy managed files as a substitute for the canonical tool.
 
-## 6. Remote sync path
+## 7. Remote compatibility path
 
-Remote orchestration is consumer configuration, not a hardcoded Core service. Read `.github/lean-core-sync.json` and require:
-
-```json
-{
-  "schemaVersion": 1,
-  "remote": {
-    "type": "github-issue-control-plane",
-    "repository": "owner/control-plane-repo",
-    "titleTemplate": "[sync-core] {owner}/{repository}",
-    "requireEmptyBody": true
-  }
-}
-```
+Remote orchestration is consumer configuration. Read `.github/lean-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.
 
-Only the placeholders `{owner}` and `{repository}` may be substituted in `titleTemplate`. Resolve them from the consumer's canonical GitHub remote. Do not put product requirements, baseline JSON, source code, secrets, or other private consumer details into the public request.
+Create exactly the configured request. Do not put product requirements, baseline JSON, source code, secrets, or other private consumer details into a public request.
 
-For `github-issue-control-plane`, create exactly one issue in the configured provider repository using the rendered title and an empty body. Use the environment's normal GitHub integration or CLI; never request or expose a long-lived Core credential merely to make the 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.
 
-The remote provider is expected to:
+If the provider cannot satisfy that contract, report `REMOTE SYNC UNAVAILABLE`; do not silently clone Core or invent another synchronization mechanism.
 
-- validate requester/target authorization,
-- obtain its own short-lived source/target credentials,
-- resolve the accepted Core source,
-- run the canonical Core sync contract against the target consumer,
-- refuse unsafe consumer drift/conflicts,
-- update exact Core provenance,
-- publish the result on a short-lived consumer branch and PR,
-- run/observe consumer CI.
+## 8. Verification
 
-If the configured provider does not support that contract, report `REMOTE SYNC UNAVAILABLE`; do not silently clone Core or invent a different synchronization mechanism.
-
-## 7. Verification
-
-### Local path
-
-After apply, run:
+For a local apply run:
 
 ```text
 python tools/lean-core/check-core-baseline.py --root .
@@ -189,32 +159,20 @@ git diff --stat
 git diff -- CORE_BASELINE.json
 ```
 
-Confirm:
-
-- managed paths match the refreshed hashes,
-- consumer-owned paths were not overwritten,
-- the baseline records the exact Core commit actually applied,
-- only the intended sync branch changed.
-
-Present the meaningful diff for human review. After acceptance, recommend `/deliver` for normal commit/push/PR/CI mechanics.
-
-### Remote path
-
-Observe the provider result when available. Report the target branch/PR and exact Core commit applied. The human reviews the consumer PR and retains the normal explicit merge/finalize gate.
+Confirm exact Core provenance, managed hashes, consumer-owned preservation, and intended branch scope. Present the meaningful diff and recommend `/deliver` after human acceptance.
 
-If the developer has a local consumer checkout, remind them to use `/pull-latest` after the remote sync PR is merged when their local working state is safe. Do not overwrite unrelated local work.
+For a remote path, report the resulting PR and exact Core commit when observed. Merge remains the normal explicit final gate.
 
-## 8. Boundaries
+## 9. Boundaries
 
 `/core-sync` never:
 
-- requires a local Core clone when a configured remote provider can perform the update,
-- modifies a dirty/diverged/intentional local Core checkout automatically,
-- uses merge/rebase/reset/force operations to refresh Core,
-- treats managed consumer drift as disposable,
-- overwrites consumer-owned paths merely because Core has a similarly named destination,
-- publishes a Core release/tag,
-- merges the consumer sync PR without the normal explicit final gate,
+- directly synchronizes Core when `LEAN_BASELINE.json` exists;
+- uses direct Core sync as a substitute for `/lean-update`;
+- modifies ambiguous local Core state;
+- treats managed consumer drift as disposable;
+- publishes Core or Lean package releases/tags;
+- merges the consumer sync PR;
 - deploys production.
 
-If reusable Core content itself is wrong, fix Core canonically instead of forking the reusable file in the consumer.
+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.