catence 0.2.0-beta.4 → 0.2.0-beta.6

package/dist/contracts/release.d.ts

@@ -3,7 +3,7 @@
  * Keep these values synchronized with release/manifest.json; release checks
  * deliberately reject drift before a package can be published.
  */
-export declare const CATENCE_RUNTIME_VERSION = "0.2.0-beta.4";
+export declare const CATENCE_RUNTIME_VERSION = "0.2.0-beta.6";
 export declare const CATENCE_PROTOCOL_VERSION = 1;
 export type CatenceRuntimeCapabilities = {
     mcp: true;

package/dist/contracts/release.js

@@ -3,7 +3,7 @@
  * Keep these values synchronized with release/manifest.json; release checks
  * deliberately reject drift before a package can be published.
  */
-export const CATENCE_RUNTIME_VERSION = '0.2.0-beta.4';
+export const CATENCE_RUNTIME_VERSION = '0.2.0-beta.6';
 export const CATENCE_PROTOCOL_VERSION = 1;
 export function catenceRuntimeHealth() {
     return {

package/dist/core/runtime/catalog.js

@@ -41,7 +41,7 @@ function legacyStoreMessage(paths) {
     return `Catence 0.2 uses a catalog at ${paths.root}. The existing directory looks like a 0.1 data store and cannot be migrated automatically. Create a fresh catalog and re-sync each athlete.`;
 }
 /** Home-directory entries the Console creates on its own and must not block catalog initialization. */
-const CONSOLE_ARTIFACTS = new Set(['config.json', 'console']);
+const CONSOLE_ARTIFACTS = new Set(['config.json', 'console', '.files', '.chainlit', 'public']);
 export async function loadCatalog(paths = resolveCatalogPaths()) {
     const contents = await readFile(paths.catalog, 'utf8').catch((error) => {
         if (error.code !== 'ENOENT')
@@ -79,8 +79,9 @@ export async function initializeCatalog(paths = resolveCatalogPaths(), athlete)
     }
     if (entries.includes('catence.duckdb'))
         throw new Error(legacyStoreMessage(paths));
-    if (entries.some((entry) => !CONSOLE_ARTIFACTS.has(entry))) {
-        throw new Error(`Refusing to initialize ${paths.root}: choose an empty --home directory or remove its unrelated contents.`);
+    const unrelated = entries.filter((entry) => !CONSOLE_ARTIFACTS.has(entry));
+    if (unrelated.length > 0) {
+        throw new Error(`Refusing to initialize ${paths.root}: found ${unrelated.join(', ')}. Remove these or choose an empty --home directory.`);
     }
     const id = athleteIdSchema.parse(athlete.id);
     const record = { id, label: athlete.label.trim(), createdAt: new Date().toISOString() };

package/docs/deployment.md

@@ -126,7 +126,7 @@ secrets are missing, prints the remaining steps and exits.
 
 ```sh
 CATENCE_CONSOLE_USERNAME=coach
-CATENCE_CONSOLE_PASSWORD_HASH='…'      # generate: docker compose ... run --rm --entrypoint /opt/catence-console/bin/catence-console console auth hash-password
+CATENCE_CONSOLE_PASSWORD_HASH='…'      # generate: ./catence-deploy/hash-password.sh
 CHAINLIT_AUTH_SECRET='…'               # generate: openssl rand -hex 32
 OPENAI_API_KEY='…'                     # or ANTHROPIC_API_KEY / OPENCODE_GO_API_KEY …
 OPENAI_API_BASE=''                     # only for OpenAI-compatible endpoints
@@ -248,8 +248,9 @@ volume and your `config.json` are preserved.
 - **"No Catence config exists"** — should not happen after a seeded deploy or
   wizard run; ensure `/data/config.json` (Docker) or `~/.catence/config.json`
   exists and contains a `console` section.
-- **"Refusing to initialize"** — the data home contains unrelated files;
-  `config.json` and `console/` are allowed, anything else blocks `setup`.
+- **"Refusing to initialize"** — the data home contains unrelated files; the
+  error lists them. Console artifacts (`config.json`, `console/`, and Chainlit's
+  `.files/`, `.chainlit/`, `public/`) are allowed; anything else blocks `setup`.
 - **Settings panel has no Model dropdown** — the Console loads profiles from
   `config.json`; write one via the wizard, a manual copy, or the discovery
   script.

package/docs/llm-providers.md

@@ -305,3 +305,26 @@ prints credential values.
 ```sh
 catence-console doctor --home "$HOME/.catence" --mcp-url http://127.0.0.1:8787/mcp
 ```
+
+## Docker: generating the Console login hash
+
+`deploy-console.sh` writes a small helper into the deployment directory. Run it
+once after the script to generate the bcrypt hash for
+`CATENCE_CONSOLE_PASSWORD_HASH` — it prompts for the password on the terminal,
+never echoes it, and uses the compose project so it works no matter what image
+tag the script built:
+
+```sh
+./catence-deploy/hash-password.sh
+```
+
+Paste the output into `CATENCE_CONSOLE_PASSWORD_HASH` in `catence-deploy/.env`,
+then start the stack (`./deploy-console.sh beta` again, or
+`docker compose -f catence-deploy/docker-compose.yml --env-file catence-deploy/.env up -d`).
+
+If you prefer, re-run the deploy script with `--generate-secrets` instead and
+answer the interactive password prompt; it saves the hash to `.env` for you.
+Without the helper (for example an older deployment), the equivalent command
+is `docker run --rm -it --entrypoint /opt/catence-console/bin/catence-console
+<image-tag> auth hash-password`, where `<image-tag>` is the tag printed by the
+script.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "catence",
-  "version": "0.2.0-beta.4",
+  "version": "0.2.0-beta.6",
   "description": "Local MCP access to normalized Garmin, Intervals.icu, and targeted Strava fitness data.",
   "license": "AGPL-3.0-or-later",
   "repository": {