@graphit/cli 0.2.379 → 0.2.384

package/skills/graphit/references/share.md

@@ -20,9 +20,9 @@ Use the **draft door** for shared dashboards and the **share plan** for private
 
 ## Shared-scope checks
 
-Read kb-scope.md for effective permissions and exact placement, kb-discovery.md for staged reuse discovery, and semantic-authoring.md plus kb-actions.md for supported definitions, equivalence and verification. Resolve the audience, lowercase group and uppercase policy key from current `status` and returned `domain_keys`; carry forward choices already made. Read access is the ceiling for writes, and a status result is advisory, never a grant.
+Read kb-scope.md for effective permissions and exact placement, kb-discovery.md for staged reuse discovery, and semantic-authoring.md plus kb-actions.md for supported definitions, equivalence and validation. Resolve the audience, lowercase group and uppercase policy key from current `status` and returned `domain_keys`; carry forward choices already made. Read access is the ceiling for writes, and a status result is advisory, never a grant.
 
-**KB-readiness gate:** before work goes live for others, confirm the required models, nested components, metrics, groups and rules exist and have the needed verification. If a business measure is missing, present its gap and proposed governed definition for approval, then author and verify the approved prerequisites. An ad-hoc business measure can be unavailable to governed-only viewers; do not silently publish it as a reusable governed answer. Compare actual binding, grain, time dimension, aggregation, filters, units and policy, not just names or SQL. A same-named conflicting asset is not equivalent: explain the difference and resolve the consequential choice. A truly equivalent accessible asset should be reused.
+**KB-readiness gate:** before work goes live for others, confirm the required models, nested components, metrics, groups and rules exist, are valid and are readable in the intended scope. If a business measure is missing, present its gap and proposed governed definition for approval, then save and read back the approved prerequisites. An ad-hoc business measure can be unavailable to governed-only viewers; do not silently publish it as a reusable governed answer. Compare actual binding, grain, time dimension, aggregation, filters, units and policy, not just names or SQL. A same-named conflicting asset is not equivalent: explain the difference and resolve the consequential choice. A truly equivalent accessible asset should be reused.
 
 Choose dashboard audience and folder through dashboard-create.md when sharing. Owners share their own; org admins/owners also any they can see. Org needs admin/owner; Team needs membership. When needed, explain Private/ORG/named scopes via kb-scope.md; keep dashboard audience separate.
 
@@ -37,9 +37,9 @@ Report 409 (another editor), 423 (locked) and 403 (view-only) with the returned
 ## Share plan: private to shared
 
 1. With the requested audience and placement established and the content checked, attempt `dashboard share` on the same ID. A success needs audience and placement readback; a private-dependency refusal supplies `blockers` and `remediation_options`. Read sharing-recovery.md. Respect `blockers_truncated` and uncertainty; the visible list is not proof of a complete closure when eligibility could not be verified. For shapes b/c without a dashboard, inspect the selected assets and their visible dependencies directly; do not invent a share-preview endpoint.
-2. For each returned private dependency, choose **reuse**, **move**, or **create**. Reuse an accessible shared equivalent only after inspecting its full definition. Move an approved model or metric with `kb update semantic-model` or `kb update metric` and the target `group`; the bound source's home follows its model, there is no independent source-move command. Create only a genuinely missing, supported definition through `kb create`, never a copy to evade ownership or a refusal. Include naming collisions and the impact of changing visibility.
+2. For each returned private dependency, choose **reuse**, **move**, or **create**. Reuse an accessible shared equivalent only after inspecting its full definition. Move an approved model or metric with `kb update semantic-model` or `kb update metric` and the target `group`, several in one ordered `kb batch`; the bound source's home follows its model, no command moves a source alone. Create only a genuinely missing, supported definition through `kb create`, never a copy to evade ownership or a refusal. Include naming collisions and visibility impact.
 3. Present the whole plan as **one structured ask**: exact assets, reuse comparisons, moves/new definitions, affected audience, group, rules and destination. Carry forward existing authorization; ask for the additional effects or consequential choices not yet approved. An authorization to share a dashboard alone does not silently authorize broadening every source's audience.
-4. Apply the approved dependency order one item at a time. Read each terminal receipt and re-read the resulting definition/binding before the next step. When reusing a shared asset, rewrite each `data-graphit-*` attribute naming the replaced asset through `dashboard update-html`, preserving unrelated content. Run the readiness checks on the resulting references and pre-flight the canvas. `dashboard check` is not proof of sharing eligibility.
+4. Apply the approved dependency order. Read each item's terminal receipt and re-read the resulting definition/binding before the next step. When reusing a shared asset, rewrite each `data-graphit-*` attribute naming the replaced asset through `dashboard update-html`, preserving unrelated content. Run the readiness checks on the resulting references and pre-flight the canvas. `dashboard check` is not proof of sharing eligibility.
 5. Retry the original `dashboard share` with the agreed space/team and `--folder-path`. Verify the same ID's audience through `dashboard list` and placement through the destination folder listing. For definitions/source-only work, read back the exact group, binding and requested configuration instead of claiming a dashboard was shared.
 6. On intermediate failure, report what applied, what remains and the returned next step. Preserve successful work. Reconcile uncertain writes by reading state before retrying; do not repeat a non-retryable operation unchanged, silently fall back to another folder, or create a replacement dashboard/source.
 

package/skills/graphit-build/SKILL.md

@@ -2,7 +2,7 @@
 name: graphit-build
 description: >-
   Author and verify Graphit dashboard content, private or shared, and build private reports, sources and saved metrics. Pair with graphit-share for shared dependencies, draft sessions and publication. Use graphit-explore for answers without artifacts.
-skill_version: "0.2.379"
+skill_version: "0.2.384"
 ---
 
 # Build: author and verify content

package/skills/graphit-explore/SKILL.md

@@ -2,7 +2,7 @@
 name: graphit-explore
 description: >-
   Answer, explain or diagnose business data using Graphit. Use after Graphit routing or for a direct Graphit question, including reads of shared dashboards. Does not authorize creating reusable definitions or sharing; use graphit-build to keep a private artifact and graphit-share for shared writes.
-skill_version: "0.2.379"
+skill_version: "0.2.384"
 ---
 
 # Explore: answer the question

package/skills/graphit-share/SKILL.md

@@ -2,7 +2,7 @@
 name: graphit-share
 description: >-
   Share or publish Graphit work, edit shared Graphit dashboards, or author into a shared group. Use after Graphit routing or a direct Graphit shared-scope request. Pair with graphit-build for dashboard authoring. Read-only questions belong to graphit-explore.
-skill_version: "0.2.379"
+skill_version: "0.2.384"
 ---
 
 # Share: checks at the shared write
@@ -47,9 +47,9 @@ Use the **draft door** for shared dashboards and the **share plan** for private
 
 ## Shared-scope checks
 
-Read ../graphit/references/kb-scope.md for effective permissions and exact placement, ../graphit/references/kb-discovery.md for staged reuse discovery, and ../graphit/references/semantic-authoring.md plus ../graphit/references/kb-actions.md for supported definitions, equivalence and verification. Resolve the audience, lowercase group and uppercase policy key from current `status` and returned `domain_keys`; carry forward choices already made. Read access is the ceiling for writes, and a status result is advisory, never a grant.
+Read ../graphit/references/kb-scope.md for effective permissions and exact placement, ../graphit/references/kb-discovery.md for staged reuse discovery, and ../graphit/references/semantic-authoring.md plus ../graphit/references/kb-actions.md for supported definitions, equivalence and validation. Resolve the audience, lowercase group and uppercase policy key from current `status` and returned `domain_keys`; carry forward choices already made. Read access is the ceiling for writes, and a status result is advisory, never a grant.
 
-**KB-readiness gate:** before work goes live for others, confirm the required models, nested components, metrics, groups and rules exist and have the needed verification. If a business measure is missing, present its gap and proposed governed definition for approval, then author and verify the approved prerequisites. An ad-hoc business measure can be unavailable to governed-only viewers; do not silently publish it as a reusable governed answer. Compare actual binding, grain, time dimension, aggregation, filters, units and policy, not just names or SQL. A same-named conflicting asset is not equivalent: explain the difference and resolve the consequential choice. A truly equivalent accessible asset should be reused.
+**KB-readiness gate:** before work goes live for others, confirm the required models, nested components, metrics, groups and rules exist, are valid and are readable in the intended scope. If a business measure is missing, present its gap and proposed governed definition for approval, then save and read back the approved prerequisites. An ad-hoc business measure can be unavailable to governed-only viewers; do not silently publish it as a reusable governed answer. Compare actual binding, grain, time dimension, aggregation, filters, units and policy, not just names or SQL. A same-named conflicting asset is not equivalent: explain the difference and resolve the consequential choice. A truly equivalent accessible asset should be reused.
 
 Choose dashboard audience and folder through ../graphit/references/dashboard-create.md when sharing. Owners share their own; org admins/owners also any they can see. Org needs admin/owner; Team needs membership. When needed, explain Private/ORG/named scopes via ../graphit/references/kb-scope.md; keep dashboard audience separate.
 
@@ -64,9 +64,9 @@ Report 409 (another editor), 423 (locked) and 403 (view-only) with the returned
 ## Share plan: private to shared
 
 1. With the requested audience and placement established and the content checked, attempt `dashboard share` on the same ID. A success needs audience and placement readback; a private-dependency refusal supplies `blockers` and `remediation_options`. Read ../graphit/references/sharing-recovery.md. Respect `blockers_truncated` and uncertainty; the visible list is not proof of a complete closure when eligibility could not be verified. For shapes b/c without a dashboard, inspect the selected assets and their visible dependencies directly; do not invent a share-preview endpoint.
-2. For each returned private dependency, choose **reuse**, **move**, or **create**. Reuse an accessible shared equivalent only after inspecting its full definition. Move an approved model or metric with `kb update semantic-model` or `kb update metric` and the target `group`; the bound source's home follows its model, there is no independent source-move command. Create only a genuinely missing, supported definition through `kb create`, never a copy to evade ownership or a refusal. Include naming collisions and the impact of changing visibility.
+2. For each returned private dependency, choose **reuse**, **move**, or **create**. Reuse an accessible shared equivalent only after inspecting its full definition. Move an approved model or metric with `kb update semantic-model` or `kb update metric` and the target `group`, several in one ordered `kb batch`; the bound source's home follows its model, no command moves a source alone. Create only a genuinely missing, supported definition through `kb create`, never a copy to evade ownership or a refusal. Include naming collisions and visibility impact.
 3. Present the whole plan as **one structured ask**: exact assets, reuse comparisons, moves/new definitions, affected audience, group, rules and destination. Carry forward existing authorization; ask for the additional effects or consequential choices not yet approved. An authorization to share a dashboard alone does not silently authorize broadening every source's audience.
-4. Apply the approved dependency order one item at a time. Read each terminal receipt and re-read the resulting definition/binding before the next step. When reusing a shared asset, rewrite each `data-graphit-*` attribute naming the replaced asset through `dashboard update-html`, preserving unrelated content. Run the readiness checks on the resulting references and pre-flight the canvas. `dashboard check` is not proof of sharing eligibility.
+4. Apply the approved dependency order. Read each item's terminal receipt and re-read the resulting definition/binding before the next step. When reusing a shared asset, rewrite each `data-graphit-*` attribute naming the replaced asset through `dashboard update-html`, preserving unrelated content. Run the readiness checks on the resulting references and pre-flight the canvas. `dashboard check` is not proof of sharing eligibility.
 5. Retry the original `dashboard share` with the agreed space/team and `--folder-path`. Verify the same ID's audience through `dashboard list` and placement through the destination folder listing. For definitions/source-only work, read back the exact group, binding and requested configuration instead of claiming a dashboard was shared.
 6. On intermediate failure, report what applied, what remains and the returned next step. Preserve successful work. Reconcile uncertain writes by reading state before retrying; do not repeat a non-retryable operation unchanged, silently fall back to another folder, or create a replacement dashboard/source.