@ouro.bot/cli 0.1.0-alpha.380 → 0.1.0-alpha.382

package/changelog.json

@@ -1,6 +1,23 @@
 {
   "_note": "This changelog is maintained as part of the PR/version-bump workflow. Agent-curated, not auto-generated. Agents read this file directly via read_file to understand what changed between versions.",
   "versions": [
+    {
+      "version": "0.1.0-alpha.382",
+      "changes": [
+        "The packaged travel-planning skill now describes travel/tool credentials as agent Bitwarden/Vaultwarden vault items instead of using retired bundle-vault wording.",
+        "Documentation contracts now block packaged skills from reintroducing legacy local credential paths, vault-key wording, or obsolete Bitwarden Agent Access CLI guidance.",
+        "The coverage workflow now treats `skills/` changes as package-shipping changes that require a fresh unpublished CLI version before merge.",
+        "`@ouro.bot/cli` and the `ouro.bot` wrapper are version-synced for the packaged skill credential-guidance release."
+      ]
+    },
+    {
+      "version": "0.1.0-alpha.381",
+      "changes": [
+        "`ouro status` provider rows now suppress old readiness error details whenever credentials are currently missing or the agent vault is unavailable, keeping the table focused on the active blocker.",
+        "Provider visibility tests now cover both missing credentials and unavailable vault credentials so stale ping failures do not reappear in status rows.",
+        "`@ouro.bot/cli` and the `ouro.bot` wrapper are version-synced for the provider status polish release."
+      ]
+    },
     {
       "version": "0.1.0-alpha.380",
       "changes": [

package/dist/heart/provider-visibility.js

@@ -101,6 +101,11 @@ function readinessLabel(readiness) {
     }
     return readiness.status;
 }
+function providerStatusDetail(lane) {
+    if (lane.credential.status !== "present")
+        return undefined;
+    return lane.readiness.error;
+}
 function formatProviderVisibilityLine(lane) {
     if (lane.status === "unconfigured") {
         return `${lane.lane}: unconfigured (${lane.reason}); repair: ${lane.repairCommand}`;
@@ -150,6 +155,7 @@ function providerVisibilityStatusRows(visibility) {
                 credential: "missing",
             };
         }
+        const detail = providerStatusDetail(lane);
         return {
             agent: visibility.agentName,
             lane: lane.lane,
@@ -157,7 +163,7 @@ function providerVisibilityStatusRows(visibility) {
             model: lane.model,
             source: lane.source,
             readiness: lane.readiness.status,
-            ...(lane.readiness.error ? { detail: lane.readiness.error } : {}),
+            ...(detail ? { detail } : {}),
             credential: credentialLabel(lane.credential),
         };
     });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ouro.bot/cli",
-  "version": "0.1.0-alpha.380",
+  "version": "0.1.0-alpha.382",
   "main": "dist/heart/daemon/ouro-entry.js",
   "bin": {
     "cli": "dist/heart/daemon/ouro-bot-entry.js",

package/skills/travel-planning.md

@@ -73,8 +73,8 @@ Present top 3-5 options comparing:
 ### Credential Handling
 
 Credentials are managed through the credential access layer, which stores
-agent-owned secrets encrypted in the bundle vault. Raw passwords never
-enter model context.
+agent-owned secrets in the agent's Bitwarden/Vaultwarden credential vault.
+Raw passwords never enter model context.
 
 - Use `credential_get` to check what credentials exist for a domain (metadata only, never passwords)
 - Use `credential_store` to save credentials the agent acquired (e.g., during sign-up for a service)