@aiaiai-pt/frankctl 0.9.7 → 0.13.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aiaiai-pt/frankctl",
-  "version": "0.9.7",
+  "version": "0.13.1",
   "description": "Terminal-first client for the Frank Low-Code Pipeline platform",
   "homepage": "https://franksdocs.nomadriver.co",
   "repository": {

package/skills/frank-cli/SKILL.md

@@ -50,7 +50,7 @@ frankctl config set profiles.default.keycloakUrl https://auth.frank.nomadriver.c
 ```
 
 Auth modes:
-- **PKCE (default)** — `frankctl auth login`. Browser-based, best for humans; uses the dedicated public `frank-cli` client unless explicitly overridden.
+- **PKCE (default)** — `frankctl auth login`. Browser-based, best for humans.
 - **Headless** — `frankctl auth login --headless --username … --password-stdin`, or inject `FRANKCTL_PASSWORD` without the stdin flag.
 - **Service account** — `frankctl auth login --service-account --client-id … --client-secret-stdin`, or inject `FRANKCTL_CLIENT_SECRET`.
 
@@ -133,9 +133,9 @@ frankctl pipelines apply -f pipeline.yaml --wait --timeout 600
 Use `--json` with `--wait` for one evidence object correlated to the exact Source
 workflow/SyncRun, Dagster/TransformRun, and ontology SyncRun started by this invocation.
 Snapshot IDs are decimal strings so JavaScript cannot round them. `status: skipped`
-means the ontology was already converged and no rows were replayed. Ontology evidence
-prefers `snapshot_id_exact`; numeric-only evidence fails closed. Use `bd entities` for
-separate target entity readback.
+means the ontology was already converged and no rows were replayed. The CLI consumes
+API v1's exact companion and exposes one canonical `snapshot_id`; unsafe numeric-only
+evidence fails closed. Use `bd entities` for separate target entity readback.
 
 ### Preflight before you apply
 
@@ -325,13 +325,10 @@ profiles:
     apiUrl: https://api.frank.nomadriver.co
     keycloakUrl: https://auth.frank.nomadriver.co
     realm: frank
-    clientId: frank-cli
+    clientId: frank-low-code
 ```
 
-Precedence (top wins): CLI flag → env var → YAML → built-in default. Browser
-PKCE's built-in client is `frank-cli`; headless password login retains
-`frank-low-code`. Stored tokens retain their issuing client id so refresh uses
-the same client.
+Precedence (top wins): CLI flag → env var → YAML → built-in default.
 `config get <key>` reports `{value, source}` so you can see which layer won;
 `config list` prints the merged effective profile.
 
@@ -405,9 +402,9 @@ frankctl bd entities <id>              # read entities back out — confirm valu
 actually materialized as entities, not just that the sync reported success.
 `bd sync --force` full-replays through REST even when the snapshot and effective
 mapping spec are unchanged. Normal output includes replay reason, row/snapshot
-evidence, and safe attempted/applied SyncSpec fingerprint prefixes. Human output
-prefers the precision-safe decimal string `snapshot_id_exact`; JSON exposes it
-alongside the legacy numeric `snapshot_id`.
+evidence, and safe attempted/applied SyncSpec fingerprint prefixes. Human and
+JSON output expose one precision-safe decimal string under `snapshot_id`; the
+API v1 legacy numeric and transitional exact fields never leak through.
 
 For an ordinary sync, the CLI falls back to BackingDataset status polling when
 an older API does not return exact-run evidence, and clearly marks replay