@platless/axom-cli 0.5.9 → 0.6.52

package/dist/credentials.js

@@ -34,6 +34,22 @@ export async function accessTokenFor(server, forceRefresh = false) {
     }
     return accessTokenFromNativeStore(server, forceRefresh);
 }
+export function peekNativeAccessToken(server) {
+    const cached = accessCache.get(server);
+    return cached?.accessToken && Date.parse(cached.expiresAt) - Date.now() >= 30_000 ? cached.accessToken : undefined;
+}
+export async function peekAccessToken(server) {
+    const fromEnv = process.env.AXOM_ACCESS_TOKEN?.trim();
+    if (fromEnv)
+        return fromEnv;
+    if (usesTestMemoryStore()) {
+        const cached = memoryStore.get(server);
+        return cached?.accessToken && Date.parse(cached.expiresAt) - Date.now() >= 30_000 ? cached.accessToken : undefined;
+    }
+    if (process.platform === 'darwin')
+        return (await requestCredentialBroker({ action: 'peek', server })).accessToken;
+    return peekNativeAccessToken(server);
+}
 export async function clearTokens(server) {
     if (usesTestMemoryStore()) {
         memoryStore.delete(server);

package/dist/install/claude/commands.js

@@ -12,7 +12,7 @@ Workflow:
 2. \`axom__app_struct__list_models\` / \`axom__app_struct__get_model\` for a model's attributes, operations, and display metadata.
 3. Prefer read-only struct tools here; do not mutate anything from this command.
 
-For the underlying concepts (applications, models, attributes, references), load guide \`concepts/data-model/index.md\` with \`axom__guide__load\`.
+For the underlying concepts (applications, models, attributes, references), see knowledge page \`concepts/data-model/index.md\` (\`axom__knowledge__get\`).
 `,
     record: `---
 description: Query, create, update, upsert, or delete Axomwork records
@@ -24,11 +24,11 @@ $ARGUMENTS
 
 Workflow:
 1. Discover structure first when unsure: \`axom__app_struct__get_model\` for attribute names and types.
-2. Query with \`axom__record_query__query_records\` (filters/sorts/page criteria — for criteria syntax, load guide \`agent-integration/mcp/record-query-criteria.md\`).
+2. Query with \`axom__record_query__query_records\` (filters/sorts/page criteria — for criteria syntax, see knowledge page \`agent-integration/mcp/record-query-criteria.md\`).
 3. Mutate with \`axom__record_write__create_record\` / \`axom__record_write__update_record\` / \`axom__record_write__upsert_record\` / \`axom__record_write__delete_record\`. Read the record first before updating; confirm with the user before deleting.
 4. \`axom__record_write__upsert_record\` needs \`identityField\` and the identity value inside \`record\`.
 
-For safe mutation patterns, load guide \`agent-integration/operating-patterns/safe-record-mutations.md\`.
+For safe mutation patterns, see knowledge page \`agent-integration/operating-patterns/safe-record-mutations.md\`.
 `,
     execute: `---
 description: Execute Axomwork operations and services, following async runs to completion
@@ -41,10 +41,10 @@ $ARGUMENTS
 Workflow:
 1. Find the operation on its model (\`axom__app_struct__get_model\`) or the service by name.
 2. Call \`axom__execute__run_operation\` (applicationName/modelName/operationName/input) or \`axom__execute__run_service\` (serviceName/input).
-3. Interpret the ExecuteResult payload: \`status\` (success/failure/running), \`message\`, \`text\`, \`returnValue\`, \`runId\`/\`runType\`, \`errors[]\` ({target,code,message}).
-4. When \`status\` is \`running\`, follow \`runId\` (see \`runType\`) until a terminal state before reporting the outcome.
+3. Interpret the ExecuteResult payload: \`status\` (success/failure/running), \`message\`, \`text\`, \`returnValue\`, \`workId\`/\`workKind\`, \`errors[]\` ({target,code,message}).
+4. When \`status\` is \`running\`, follow \`workId\` (see \`workKind\`) until a terminal state before reporting the outcome.
 
-For sync-vs-job semantics load guide \`concepts/execution/synchronous-and-task-execution.md\`; for run following load guide \`agent-integration/operating-patterns/following-runs.md\`.
+For sync-vs-job semantics see knowledge page \`concepts/execution/synchronous-and-task-execution.md\`; for run following see knowledge page \`agent-integration/operating-patterns/following-runs.md\`.
 `,
     definition: `---
 description: Develop Axomwork definitions — apps, models, attributes, operations, workflows (requires app_studio scope and an admin account)
@@ -56,8 +56,8 @@ $ARGUMENTS
 
 Rules:
 1. ETag workflow: read the resource first, send its \`etag\` back as \`expectedEtag\` (bodies use \`expectedBodyEtag\`). On conflict, re-read and merge intentionally.
-2. Before authoring \`.axom.kts\` script bodies, load guide \`script-language/sdk/index.md\`; workflow DSL: \`script-language/workflows/index.md\`; sync/job/streaming patterns: \`script-language/patterns/index.md\`.
-3. For definition semantics (apps, models, attributes, operations, workflows), load guide \`application-development/index.md\`.
+2. Before authoring \`.axom.kts\` script bodies, see knowledge page \`script-language/sdk/index.md\`; workflow DSL: \`script-language/workflows/index.md\`; sync/job/streaming patterns: \`script-language/patterns/index.md\`.
+3. For definition semantics (apps, models, attributes, operations, workflows), see knowledge page \`application-development/index.md\`.
 4. Confirm destructive definition deletes with the user first.
 `,
     platform: `---
@@ -70,20 +70,20 @@ $ARGUMENTS
 
 Rules:
 1. Read current configuration before editing; respect ETag guards where tools expose them.
-2. For configuration semantics (AI providers and profiles, cowork agents, datasources, platform skills and settings), load guide \`platform-operations/index.md\` first.
+2. For configuration semantics (AI providers and profiles, cowork agents, datasources, platform skills and settings), see knowledge page \`platform-operations/index.md\` first.
 3. Confirm with the user before changes that can interrupt running workflows or agent sessions.
 `,
-    guide: `---
-description: Look something up in the Axomwork Guide (platform manual)
+    knowledge: `---
+description: Look something up in the Axomwork manual
 ---
 
-Answer using the Axomwork Guide:
+Answer using the Axomwork manual:
 
 $ARGUMENTS
 
 Workflow:
-1. \`axom__guide__search\` with keywords or the question itself; read the ranked snippets.
-2. \`axom__guide__load\` a hit's \`path\` for the full page (omit \`path\` for the table of contents).
-3. Answer from guide content and cite the guide paths you used. If the guide has no answer, say so and fall back to tool discovery (\`tools/list\`).
+1. \`axom__knowledge__search\` with keywords or the question itself; read the ranked snippets.
+2. \`axom__knowledge__get\` a hit's \`path\` for the full page (omit \`path\` for the table of contents).
+3. Answer from the manual and cite the knowledge page paths you used. If the manual has no answer, say so and fall back to tool discovery (\`tools/list\`).
 `,
 };