@uxnan/shared 0.0.8-alpha.20260720 → 0.0.10-alpha.20260724

package/README.md

@@ -52,7 +52,7 @@ flowchart TB
 | JSON-RPC | envelope types + constructors (`makeRequest`, `makeNotification`, `makeResponse`, `makeErrorResponse`), error codes (`JsonRpcErrorCode` + Uxnan-specific `-32000..-32008`), `RpcError`, typed method registry (`JsonRpcMethodRegistry` + `METHOD_NAMES`), `isKnownMethod` |
 | Streaming | `StreamNotification` enum + param types (`TurnStartedParams`, `MessageDeltaParams`, `ThinkingDeltaParams`, `ContentBlockParams`, `TurnCompletedParams`, `TurnUsage`, `TurnErrorParams`, `TurnAbortedParams`, `ModelResolvedParams`) |
 | E2EE | handshake messages (`clientHello` / `serverHello` / `clientAuth` / `ready`), `buildHandshakeTranscript`, `SecureEnvelope`, `PairingPayload` v2 (`relay` optional + `hosts: string[]`) with `Base64(utf8(JSON))` QR encoding |
-| Models | thread / turn / message (with `MessageContent` polymorphic blocks), git, workspace (incl. `browseDirs` + `exists`), project, auth, session/trust (`BridgeStatus` incl. `latestVersion?`/`updateAvailable?`), approval, question (interactive multiple-choice) |
+| Models | thread / turn / message (with `MessageContent` polymorphic blocks), git, workspace (incl. `browseDirs` + `exists`), project, auth, session/trust (`BridgeStatus` incl. `latestVersion?`/`updateAvailable?`), bridge-owned profile metrics (complete-ledger export/import), approval, question (interactive multiple-choice) |
 | Agents | `IAgentAdapter` (with `respondApproval`, `listModels`, `nativeSessionId`, `SendTurnOptions { threadId, turnId, text, service?, effort?, options?, attachments?, cwd?, accessMode? }`), `AgentModel` (incl. `version?`, `isDefault?`, `options?`, `contextWindow?`, `isLatestAlias?`), `AgentCapabilities` (incl. `images`, `approvals`, `reportsContextUsage`), `AgentConfig` (cwd, agentId, model, plus optional `binaryPath`/`extraArgs`) |
 | Version | `compareVersions` / `isNewerVersion` — dependency-free SemVer precedence (used by the bridge's npm update check) |
 | Validation | Ajv validators for requests, responses, envelopes, pairing payload, push payloads |

package/dist/src/agents/agent-capabilities.d.ts

@@ -91,8 +91,8 @@ export interface AgentModelOption {
  * A selectable model an agent reports, returned by `agent/models`.
  *
  * `id` is the wire value passed back to the agent for routing — a stable alias
- * for Claude Code (`opus`/`sonnet`/`haiku`), a `provider/model` id for OpenCode,
- * or a concrete model id for Codex. `displayName`, `description`, `version` and
+ * for Claude Code (`fable`/`opus`/`sonnet`/`haiku`), a `provider/model` id for
+ * OpenCode, or a concrete model id for Codex. `displayName`, `description`, `version` and
  * `isDefault` are presentation hints; consumers must tolerate any of them being
  * absent (older bridges report bare id strings).
  */
@@ -105,7 +105,7 @@ export interface AgentModel {
     description?: string;
     /**
      * Concrete underlying version when `id` is an alias that resolves to a
-     * moving target — e.g. Claude Code's `opus` → `claude-opus-4-8`. Surfaced so
+     * moving target — e.g. Claude Code's `opus` → `claude-opus-5`. Surfaced so
      * the user can see which exact model an alias currently maps to.
      */
     version?: string;
@@ -125,11 +125,12 @@ export interface AgentModel {
      */
     contextWindow?: number;
     /**
-     * Marks a moving-target "latest" alias (Claude Code's `opus`/`sonnet`/`haiku`,
-     * each of which always routes to the newest version of that tier the account
-     * can use — see {@link version} for the resolved concrete id). Concrete/pinned
-     * models leave this absent. Presentation-only: lets a client offer to
-     * hide the aliases and show exact versions only, without hardcoding ids.
+     * Marks a moving-target "latest" alias (Claude Code's
+     * `fable`/`opus`/`sonnet`/`haiku`, each of which always routes to the newest
+     * version of that tier the account can use — see {@link version} for the
+     * resolved concrete id). Concrete/pinned models leave this absent.
+     * Presentation-only: lets a client offer to hide the aliases and show exact
+     * versions only, without hardcoding ids.
      */
     isLatestAlias?: boolean;
 }

package/dist/src/models/metrics.d.ts

@@ -6,10 +6,10 @@
  * agents/models used, connection time, git actions, an activity heatmap). Those
  * were derived on the phone from local storage and so were lost on an app
  * uninstall (the app has no cloud login). To make them durable, the **bridge**
- * becomes the source of truth: it computes them from its own authoritative data
- * (the conversation store) plus persisted session + git-action event logs it
- * observes itself, and serves them over `metrics/get`. The phone renders one
- * snapshot per PC and sums across PCs.
+ * becomes the source of truth: it persists a complete activity ledger
+ * (conversations, turns/messages, reported tokens, sessions and Git actions)
+ * and serves it over `metrics/get`. Deleting mutable conversation history does
+ * not subtract activity. The phone renders one snapshot per PC and sums PCs.
  *
  * A `metrics/export` produces an opaque, tamper-proof file only the SAME bridge
  * can later verify + decrypt (AES-256-GCM under a secret held in the PC's OS
@@ -76,10 +76,9 @@ export interface MetricsActivityDay {
 }
 /**
  * Aggregated metrics for ONE PC (the bridge that returns it), built from the
- * bridge's own authoritative data: the conversation store (threads/turns) plus
- * its persisted session + git-action event logs. The phone renders this per PC
- * and sums across PCs for the all-PCs profile. Every field is a count the phone
- * cannot inflate — the bridge observes it. Source of `metrics/get`.
+ * bridge's durable activity ledger. The phone renders this per PC and sums
+ * across PCs for the all-PCs profile. Every field is a count the phone cannot
+ * inflate — the bridge observes and retains it. Source of `metrics/get`.
  */
 export interface MetricsSnapshot {
     /** Schema version, for forward-compatible parsing. */
@@ -123,7 +122,7 @@ export interface MetricsSnapshot {
     updatedAt: number;
 }
 /**
- * `metrics/export` request. The bridge seals its metrics event log into an
+ * `metrics/export` request. The bridge seals its complete metrics ledger into an
  * opaque, tamper-proof blob that only THIS same bridge can later verify +
  * decrypt (AES-256-GCM under a secret held in the OS keychain). An optional user
  * [passphrase] adds a second confidentiality layer (scrypt-derived), so a leaked
@@ -145,8 +144,8 @@ export interface MetricsExportResult {
  * `metrics/import` request. The phone sends back a previously exported [blob].
  * The bridge verifies it was sealed by THIS PC — a foreign or edited file is
  * rejected — decrypts it (using [passphrase] when the file was passphrase-locked)
- * and merges its events by id (idempotent: re-importing the same file changes
- * nothing). Returns the refreshed snapshot.
+ * and merges its ledger rows by id (idempotent: re-importing the same file
+ * changes nothing). Returns the refreshed snapshot.
  */
 export interface MetricsImportParams {
     /** The sealed blob produced by a prior `metrics/export` on this PC. */
@@ -155,7 +154,7 @@ export interface MetricsImportParams {
     passphrase?: string;
 }
 export interface MetricsImportResult {
-    /** How many new session + git-action events were merged in. */
+    /** How many ledger rows were inserted or advanced. */
     imported: number;
     /** The refreshed snapshot after the merge. */
     snapshot: MetricsSnapshot;

package/dist/src/models/metrics.js

@@ -6,10 +6,10 @@
  * agents/models used, connection time, git actions, an activity heatmap). Those
  * were derived on the phone from local storage and so were lost on an app
  * uninstall (the app has no cloud login). To make them durable, the **bridge**
- * becomes the source of truth: it computes them from its own authoritative data
- * (the conversation store) plus persisted session + git-action event logs it
- * observes itself, and serves them over `metrics/get`. The phone renders one
- * snapshot per PC and sums across PCs.
+ * becomes the source of truth: it persists a complete activity ledger
+ * (conversations, turns/messages, reported tokens, sessions and Git actions)
+ * and serves it over `metrics/get`. Deleting mutable conversation history does
+ * not subtract activity. The phone renders one snapshot per PC and sums PCs.
  *
  * A `metrics/export` produces an opaque, tamper-proof file only the SAME bridge
  * can later verify + decrypt (AES-256-GCM under a secret held in the PC's OS

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uxnan/shared",
-  "version": "0.0.8-alpha.20260720",
+  "version": "0.0.10-alpha.20260724",
   "description": "Shared JSON-RPC and E2EE contracts for the Uxnan ecosystem (bridge, relay, mobile).",
   "license": "MPL-2.0",
   "author": "Luis Donaldo Gamas Vazquez",