@intentic/constants 1.224.0 → 1.226.0

package/README.md

@@ -9,17 +9,17 @@ The ports, paths and image references the daemon, the CLIs and the desktop app a
 
 ## Key files
 
-- [src/index.ts](src/index.ts) — the constants themselves: ports, the fixed directory layouts, legal and origin
+- [src/index.ts](src/index.ts), the constants themselves: ports, the fixed directory layouts, legal and origin
   values. Isomorphic, imported by browser code, so nothing here may touch `node:fs`.
-- [src/node.mjs](src/node.mjs) — `repoRoot()` and `packageRoot()`, behind the `@intentic/constants/node`
+- [src/node.mjs](src/node.mjs): `repoRoot()` and `packageRoot()`, behind the `@intentic/constants/node`
   subpath. Node-only, and hand-written JavaScript rather than compiled TypeScript.
 
 ## How it fits
 
 The bottom of the dependency graph: it imports nothing and almost everything imports it. A port number that lives
 in two files is a port number that will eventually be two different numbers, which is the entire argument for
-this package existing. The same argument covers the directory layouts — `/work`, `/history`, `.intentic`,
-`/opt/intentic` — which were previously typed out by hand across dozens of files with nothing linking the copies.
+this package existing. The same argument covers the directory layouts: `/work`, `/history`, `.intentic`,
+`/opt/intentic`: which were previously typed out by hand across dozens of files with nothing linking the copies.
 
 The two root-finders answer the other half of that problem. Code used to locate the repo root by counting how
 deep it sat (`../..`, `../../..`, `../../../..`), a number correct only for the file's current depth and checked
@@ -30,22 +30,22 @@ by nothing. Walking up to a marker has no such coupling, so a file can move anyw
 - If a constant is used by exactly one package, it belongs in that package. This is for the ones that cross a
   boundary.
 - `src/node.mjs` is plain JavaScript with a hand-written `.d.mts` **on purpose**. Its earliest callers run before
-  anything is built — the prepass is what performs the build, and the byte and path checks run ahead of it — so a
+  anything is built (the prepass is what performs the build, and the byte and path checks run ahead of it) so a
   helper importable only from `dist/` is one they cannot import at all, which is how a second copy of the walk
   gets written. It is also why the root `package.json` depends on this package: without that link, scripts under
   `_tools/scripts/` cannot resolve it by name.
 - **The name only resolves once `pnpm install` has run**, because a bare specifier is looked up through
-  `node_modules`. The two callers that run before any install — `prepass.mjs --checks-only`, which the `pre-push`
-  hook and the CI `preflight` job invoke on a bare checkout — therefore import `../constants/src/node.mjs` by
+  `node_modules`. The two callers that run before any install: `prepass.mjs --checks-only`, which the `pre-push`
+  hook and the CI `preflight` job invoke on a bare checkout: therefore import `../constants/src/node.mjs` by
   path. Same file, same single copy of the walk, no install required. Everything that runs after the install
   imports it by name.
-- **Extensions cannot import this package** — the boundary rule (`.oxlintrc.json`, `_extensions/README.md`) allows
+- **Extensions cannot import this package**: the boundary rule (`.oxlintrc.json`, `_extensions/README.md`) allows
   them only the SDK halves and `@intentic/sandbox-contract`, so an extension can't couple itself to app or engine
   internals. That rule stands; the contract package re-exports the four layout constants so extensions can still
   name a location instead of spelling it. One definition, reached by two paths.
 - `WORKSPACE_ROOT` and `HISTORY_ROOT` are **defaults, not laws**. The daemon takes both as overridable config and
   an isolated turn re-points them, so code holding a `Config` must read the config value. The constants are what
   that config defaults to, and what code with no config in reach can still name correctly.
-- Prefer the daemon's own `statePath()` over joining `STATE_DIR` by hand wherever it is reachable — it is typed
+- Prefer the daemon's own `statePath()` over joining `STATE_DIR` by hand wherever it is reachable: it is typed
   against the table of state files, so it catches a name the table doesn't declare. `STATE_DIR` is for callers
   outside that table.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@intentic/constants",
-  "version": "1.224.0",
-  "description": "Shared constants for the intentic packages — ports, paths, and image references the daemon, CLIs and desktop app all agree on",
+  "version": "1.226.0",
+  "description": "Shared constants for the intentic packages, ports, paths, and image references the daemon, CLIs and desktop app all agree on",
   "license": "MIT",
   "type": "module",
   "repository": {

package/src/node.mjs

@@ -7,7 +7,7 @@ import { fileURLToPath } from "node:url";
  * Two dozen files used to work out where the monorepo root was by counting how deep they sat: `../..` from a
  * package's own directory, `../../..` from its `src/`, `../../../..` from the installer scripts. Every one of
  * those numbers is correct only for the file's CURRENT depth, and nothing anywhere checks it. Move the file
- * one directory and it silently resolves somewhere else — no import fails, no type breaks; you find out when
+ * one directory and it silently resolves somewhere else: no import fails, no type breaks; you find out when
  * something reads the wrong .env at runtime, or reads nothing and falls back to a default.
  *
  * Walking up until a marker appears has none of that coupling. A file can sit at any depth, move between
@@ -22,7 +22,7 @@ import { fileURLToPath } from "node:url";
  *
  * A caller that runs before `pnpm install` has one more constraint: `@intentic/constants/node` is a BARE
  * specifier and bare specifiers resolve through node_modules, which a bare checkout has none of. Those callers
- * — `prepass.mjs`, run by the pre-push hook and by CI's preflight job — import THIS FILE by relative path
+ * (`prepass.mjs`, run by the pre-push hook and by CI's preflight job) import THIS FILE by relative path
  * instead. Still one walk; only the way in differs.
  *
  * NOT EXPORTED FROM THE PACKAGE INDEX, and that is deliberate: the index is imported by browser code
@@ -51,7 +51,7 @@ const startDir = (from) => {
 };
 
 // Walk up from `dir` until `marker` is found beside us, or we run out of parents. Returns "" for not-found so
-// each caller decides whether that is fatal — the installers treat it as "not run from a checkout" and carry
+// each caller decides whether that is fatal: the installers treat it as "not run from a checkout" and carry
 // on, while everything inside the repo treats it as impossible and throws.
 const walkUp = (dir, marker) => {
     let current = dir;
@@ -63,7 +63,7 @@ const walkUp = (dir, marker) => {
     }
 };
 
-/* THE MONOREPO ROOT, from anywhere inside it. Pass `import.meta.url` — the caller's own location is the only
+/* THE MONOREPO ROOT, from anywhere inside it. Pass `import.meta.url`: the caller's own location is the only
  * thing this needs, and it is the one thing every module already knows about itself.
  *
  * Throws when the marker is nowhere above the caller, which inside this repo means the checkout is broken. The
@@ -71,11 +71,11 @@ const walkUp = (dir, marker) => {
  * wrong directory is how a config loader silently reads no .env and every credential arrives empty. */
 export const repoRoot = (from) => {
     const found = walkUp(startDir(from), REPO_MARKER);
-    if (found === "") throw new Error(`repoRoot: no ${REPO_MARKER} above ${startDir(from)} — is this a complete checkout?`);
+    if (found === "") throw new Error(`repoRoot: no ${REPO_MARKER} above ${startDir(from)}, is this a complete checkout?`);
     return found;
 };
 
-/* THE CALLING PACKAGE'S OWN ROOT — the directory its package.json sits in. The other thing the dot-counting
+/* THE CALLING PACKAGE'S OWN ROOT: the directory its package.json sits in. The other thing the dot-counting
  * was reaching for: `createRequire(import.meta.url)("../../package.json")` in three different version.ts files,
  * each with a different number of dots because each sat at a different depth, all of them meaning "mine".
  *