@mnstry/atelier 0.2.0-alpha.8 → 0.2.0-alpha.9

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## 0.2.0-alpha.9
+
+### Fixed
+
+- The maintenance service process could not start from the shipped package:
+  its entry awaits the command contributions at top level, and the selection
+  contribution shipped in 0.2.0-alpha.8 reaches the entry again through
+  `opening.mjs` → `lifecycle.mjs`, so the process deadlocked on its own await
+  and exited 13 before it listened. `SERVICE_ENTRY_PATH` now lives in its own
+  module that nothing else depends on, and a test spawns the real entry.
+
 ## 0.2.0-alpha.8
 
 ### Added

package/README.md

@@ -54,7 +54,7 @@ governed projections
 You can see the complete loop in a disposable sample workspace:
 
 ```bash
-npm install --save-dev @mnstry/atelier@0.2.0-alpha.8
+npm install --save-dev @mnstry/atelier@0.2.0-alpha.9
 npx mnstry-atelier init --fixture=sample-workspace --target ./sample
 npx mnstry-atelier graph --project ./sample/atelier.project.json
 npx mnstry-atelier project --project ./sample/atelier.project.json
@@ -378,7 +378,7 @@ Node.js `>=22.18.0 <23` is required. Pin the prerelease while the package
 remains in alpha:
 
 ```bash
-npm install --save-dev @mnstry/atelier@0.2.0-alpha.8
+npm install --save-dev @mnstry/atelier@0.2.0-alpha.9
 ```
 
 Then choose the path that matches what you are building:
@@ -397,7 +397,7 @@ Then choose the path that matches what you are building:
 
 ## Status and command reference
 
-Current package: `@mnstry/atelier@0.2.0-alpha.8`.
+Current package: `@mnstry/atelier@0.2.0-alpha.9`.
 
 The alpha package is usable and contract-tested, but its library API may still
 change before a stable release. Pin the exact version in production toolchains.

package/docs/install.md

@@ -34,19 +34,19 @@ The registry is the distribution channel of record, as `docs/continuity.md`
 commits:
 
 ```bash
-npm install --save-dev @mnstry/atelier@0.2.0-alpha.8
+npm install --save-dev @mnstry/atelier@0.2.0-alpha.9
 ```
 
 Installing from the matching Git tag resolves to the same reviewed commit:
 
 ```bash
-npm install --save-dev "git+https://github.com/MNSTRY/atelier.git#v0.2.0-alpha.8"
+npm install --save-dev "git+https://github.com/MNSTRY/atelier.git#v0.2.0-alpha.9"
 ```
 
 Or over SSH:
 
 ```bash
-npm install --save-dev "git+ssh://git@github.com/MNSTRY/atelier.git#v0.2.0-alpha.8"
+npm install --save-dev "git+ssh://git@github.com/MNSTRY/atelier.git#v0.2.0-alpha.9"
 ```
 
 Keep the `@mnstry/` scope — see the command-form note above for why the

package/docs/upgrade.md

@@ -9,6 +9,14 @@ workspace between Atelier package releases. The flow is local-only: it does not
 provision repositories, contact a Git host, mutate the MNSTRY runtime, or write
 through a browser view.
 
+## Upgrading to 0.2.0-alpha.9
+
+This release fixes a defect in 0.2.0-alpha.8: the Obsidian maintenance service
+could not start from the published package (`atelier obsidian service start`
+reported `start-failed` with `service-exited-13`). Upgrade from 0.2.0-alpha.8
+directly; nothing else changes and no project or machine setting needs to be
+touched. 0.2.0-alpha.8 is deprecated.
+
 ## Upgrading to 0.2.0-alpha.8
 
 This release adds typed advisory decision contracts and an experimental,
@@ -158,7 +166,7 @@ For registry installs, pin the exact version and record the resolved version
 in the lockfile:
 
 ```bash
-npm install --save-dev @mnstry/atelier@0.2.0-alpha.8
+npm install --save-dev @mnstry/atelier@0.2.0-alpha.9
 npx mnstry-atelier lock write --project ./atelier.project.json
 ```
 
@@ -166,7 +174,7 @@ For Git installs, pin the release tag rather than a branch, so the lock file
 records exactly what was reviewed:
 
 ```bash
-npm install --save-dev "git+https://github.com/MNSTRY/atelier.git#v0.2.0-alpha.8"
+npm install --save-dev "git+https://github.com/MNSTRY/atelier.git#v0.2.0-alpha.9"
 npx mnstry-atelier lock write --project ./atelier.project.json
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mnstry/atelier",
-  "version": "0.2.0-alpha.8",
+  "version": "0.2.0-alpha.9",
   "private": false,
   "description": "Local toolkit that turns a Git repository into an ontology-governed knowledge graph, enforcement layer, and runtime for people, agents, and tools. No telemetry or required hosted account; optional host-bound vault adapters.",
   "keywords": [

package/src/commands/obsidian.mjs

@@ -143,7 +143,7 @@ export async function runObsidianCommandForOracleTests(options = {}, rules = {})
     const serviceSeam = async () => {
       if (seams !== null) { if (typeof seams.service?.entryPath !== 'string') refuse('seams-required', 'the service seam names the entry this command may start'); return seams.service }
       if (flags.adapter !== PRODUCTION_ADAPTER) refuse('app-adapter-not-selected', 'no editor adapter was selected; a service that reaches the installed app is never a default')
-      const { SERVICE_ENTRY_PATH } = await import('../runtime/obsidian/service-main.mjs')
+      const { SERVICE_ENTRY_PATH } = await import('../runtime/obsidian/service-entry-path.mjs')
       return { entryPath: SERVICE_ENTRY_PATH, entryArgs: [`--adapter=${PRODUCTION_ADAPTER}`] }
     }
     const appSeams = async () => {

package/src/runtime/obsidian/lifecycle.mjs

@@ -8,7 +8,7 @@ import { ensureWorkspaceIdentity } from './machine-settings.mjs'
 import { acquirePrivateGenerationLock, createAbandonmentProof, isProcessAlive } from './private-lock.mjs'
 import { processRunsRecordedExecutable } from './process-identity.mjs'
 import { DEFAULT_PROBE_TIMEOUT_MS, LOOPBACK_HOSTS, probeHealth, requestLoopback } from './service-client.mjs'
-import { SERVICE_ENTRY_PATH } from './service-main.mjs'
+import { SERVICE_ENTRY_PATH } from './service-entry-path.mjs'
 import {
   CONSENT_COVERAGES, SERVICE_SETTINGS_SCHEMA, executableIdentity, openServiceLog, publicRecord, readServiceRecord, readServiceSettings, removeServiceRecord,
   serviceNameFor, servicePaths, writeServiceSettings,

package/src/runtime/obsidian/service-entry-path.mjs

@@ -0,0 +1,9 @@
+import { fileURLToPath } from 'node:url'
+
+// The absolute path of the maintenance service entry, kept in its own module
+// so that nothing which needs the path has to import the entry itself. The
+// entry awaits at top level (it loads the command contributions before it
+// serves), and a module that both reaches it through a static import and is
+// itself reached by that load would deadlock the process: the contribution
+// graph waits for the entry, the entry waits for the contribution graph.
+export const SERVICE_ENTRY_PATH = fileURLToPath(new URL('./service-main.mjs', import.meta.url))

package/src/runtime/obsidian/service-main.mjs

@@ -33,7 +33,9 @@ const ADAPTERS = Object.freeze({
   },
 })
 
-export const SERVICE_ENTRY_PATH = fileURLToPath(import.meta.url)
+import { SERVICE_ENTRY_PATH } from './service-entry-path.mjs'
+
+export { SERVICE_ENTRY_PATH }
 export const EXIT_REFUSED = 2
 
 const log = (entry) => { try { process.stdout.write(`${JSON.stringify(entry)}\n`) } catch { /* a closed log never ends the service */ } }
@@ -68,7 +70,7 @@ export function serviceOptionsFromArgv(argv, { env = process.env } = {}) {
   }
 }
 
-const invokedDirectly = (() => { try { return Boolean(process.argv[1]) && fs.realpathSync(process.argv[1]) === fs.realpathSync(SERVICE_ENTRY_PATH) } catch { return false } })()
+const invokedDirectly = (() => { try { return Boolean(process.argv[1]) && fs.realpathSync(process.argv[1]) === fs.realpathSync(fileURLToPath(import.meta.url)) } catch { return false } })()
 
 if (invokedDirectly) {
   let options = null

package/templates/external-project-workspace/pack-lifecycle.json

@@ -6,7 +6,7 @@
       "version": "v1",
       "digest": "sha256:0eff795765e0bbd4c2510acda2e492201c23bc870df6c354eef623484643ab11",
       "compatibleRootVersions": [
-        "0.2.0-alpha.8"
+        "0.2.0-alpha.9"
       ],
       "status": "active"
     }