records-cli 0.0.2 → 0.0.3

package/dist/client.d.ts

@@ -1,5 +1,5 @@
 /** Fixed production origin — not configurable. */
-export declare const RECORDS_ORIGIN = "https://records-api.tolkee.dev";
+export declare const RECORDS_ORIGIN = "https://api-records.tolkee.dev";
 export type ClientOptions = {
     baseUrl: string;
     token?: string;

package/dist/client.js

@@ -1,5 +1,5 @@
 /** Fixed production origin — not configurable. */
-export const RECORDS_ORIGIN = "https://records-api.tolkee.dev";
+export const RECORDS_ORIGIN = "https://api-records.tolkee.dev";
 export class ApiError extends Error {
     status;
     body;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "records-cli",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "description": "Command-line interface to Records for automation and LLM agents.",
   "type": "module",
   "bin": {

package/skill/SKILL.md

@@ -1,8 +1,9 @@
 ---
 
 ## name: records-cli
+
 description: How to record new knowledge for the user via the Records CLI—create groups and records so ideas from the chat become stored documents. Use when the user asks to save, remember, or record something from the conversation, or when you should persist an explanation (lesson, reference, how-to) for later.
-compatibility: Requires the `records-cli` npm package (or a local build). Uses HTTPS against `https://records-api.tolkee.dev` only. Commands that change data need a token; ask the user if you do not have one.
+compatibility: Requires the `records-cli` npm package (or a local build). Uses HTTPS against `https://api-records.tolkee.dev` only. Commands that change data need a token; ask the user if you do not have one.
 metadata:
   cli-package: records-cli
   spec-version: "1.0"
@@ -12,7 +13,7 @@ metadata:
 ## Install and environment
 
 - **Package:** `records-cli` — install with `npm install -g records-cli` or run ad hoc with `npx records-cli`.
-- **Server:** always `https://records-api.tolkee.dev` (not configurable).
+- **Server:** always `https://api-records.tolkee.dev` (not configurable).
 - **Token:** For commands that mutate or list protected data, pass `-t <token>` or set `RECORDS_TOKEN` to the user’s plaintext key.
 - **If you do not already have a key**, ask the user before running protected commands. Do not guess or fabricate a key. Once they share it, use it only for CLI invocations and avoid repeating the full secret in replies when unnecessary.
 - If the user has no key yet, they may create one through their usual Records setup, or—where the server allows it—via the bootstrap flow described in the reference (creating the first key when none exist).

package/skill/references/REFERENCE.md

@@ -9,7 +9,7 @@
 | `-p, --pretty`        | —               | Pretty-print JSON on stdout          |
 
 
-All requests use `**https://records-api.tolkee.dev`** as the origin (fixed).
+All requests use `**https://api-records.tolkee.dev`** as the origin (fixed).
 
 Successful responses are JSON on **stdout** (usually `{ "data": … }`). Failures print JSON with `error` (and `status` / `body` when available) on **stdout**; the process exits non-zero.