@mnstry/atelier 0.2.0-alpha.14 → 0.2.0-alpha.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mnstry/atelier",
-  "version": "0.2.0-alpha.14",
+  "version": "0.2.0-alpha.15",
   "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": [
@@ -57,6 +57,8 @@
     "./cli": "./src/cli/run.mjs",
     "./project": "./src/project/config.mjs",
     "./graph": "./src/graph/graph.mjs",
+    "./graph-workspace": "./src/graph-workspace/index.mjs",
+    "./graph-workspace/browser": "./src/graph-workspace/browser/index.mjs",
     "./projection": "./src/projection/project.mjs",
     "./readiness": "./src/readiness/readiness.mjs",
     "./readiness-protocols": "./src/readiness-protocols/bundled-pack.mjs",
@@ -146,7 +148,15 @@
     "./ingestion/jev": "./src/ingestion/optional/jev/composition-binding.mjs",
     "./ingestion/jev/judgments": "./src/ingestion/optional/jev/judgments.mjs",
     "./ingestion/graphify": "./src/ingestion/optional/graphify/composition-binding.mjs",
-    "./ingestion/lightrag": "./src/ingestion/optional/lightrag/composition-binding.mjs"
+    "./ingestion/lightrag": "./src/ingestion/optional/lightrag/composition-binding.mjs",
+    "./extensions": "./src/extensions/contracts.mjs",
+    "./extensions/client": "./src/extensions/client.mjs",
+    "./extensions/server": "./src/extensions/server.mjs",
+    "./extensions/postgres": "./src/extensions/postgres.mjs",
+    "./contracts/atelier-extension-manifest.v1.schema.json": "./contracts/atelier-extension-manifest.v1.schema.json",
+    "./extensions/drizzle": "./src/extensions/drizzle.mjs",
+    "./extensions/prisma": "./src/extensions/prisma.mjs",
+    "./extensions/convex": "./src/extensions/convex.mjs"
   },
   "scripts": {
     "contract": "node src/check-atelier-export-contract.mjs",
@@ -166,7 +176,7 @@
     "collaboration:test": "node --test test/collaboration-ledger.test.mjs test/server-proposals.test.mjs",
     "sync:test": "node --test test/runtime-git-adapter.test.mjs test/runtime-observation.test.mjs test/runtime-supervisor.test.mjs",
     "boundary:test": "node --test test/boundary-policy-contract.test.mjs test/boundary-content-rules.test.mjs test/boundary-guard.test.mjs",
-    "obsidian:test": "node --test --test-concurrency=1 test/obsidian-acceptance.test.mjs test/obsidian-contract.test.mjs test/obsidian-direct-unheld.test.mjs test/obsidian-edits.test.mjs test/obsidian-first-open-real-app.test.mjs test/obsidian-login-item.test.mjs test/obsidian-maintenance.test.mjs test/obsidian-materialization.test.mjs test/obsidian-open.test.mjs test/obsidian-package.test.mjs test/obsidian-plugin.test.mjs test/obsidian-proposals.test.mjs test/obsidian-publication-feasibility.test.mjs test/obsidian-recovery.test.mjs test/obsidian-vault-layout.test.mjs test/obsidian-vault-location.test.mjs test/obsidian-views.test.mjs test/obsidian-only-you.test.mjs",
+    "obsidian:test": "node --test --test-concurrency=1 test/obsidian-acceptance.test.mjs test/obsidian-contract.test.mjs test/obsidian-direct-unheld.test.mjs test/obsidian-edits.test.mjs test/obsidian-first-open-real-app.test.mjs test/obsidian-login-item.test.mjs test/obsidian-maintenance.test.mjs test/obsidian-materialization.test.mjs test/obsidian-open.test.mjs test/obsidian-package.test.mjs test/obsidian-plugin.test.mjs test/obsidian-proposals.test.mjs test/obsidian-instance-fixture.test.mjs test/obsidian-recovery.test.mjs test/obsidian-vault-layout.test.mjs test/obsidian-vault-location.test.mjs test/obsidian-views.test.mjs test/obsidian-only-you.test.mjs",
     "upgrade:test": "node --test test/upgrade-contract.test.mjs test/upgrade.test.mjs",
     "release:audit": "node scripts/check-release-tarball.mjs",
     "release:candidate": "node scripts/release-candidate.mjs",
@@ -182,14 +192,17 @@
   "dependencies": {
     "ajv": "8.20.0",
     "ajv-formats": "3.0.1",
-    "fast-uri": "3.1.8"
+    "fast-uri": "3.1.9"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
-    "esbuild": "0.25.12",
+    "esbuild": "0.28.2",
+    "graphology": "0.25.4",
+    "graphology-layout-forceatlas2": "0.10.1",
     "playwright": "1.55.1",
-    "react": "19.1.0",
-    "react-dom": "19.1.0",
+    "react": "19.3.1",
+    "react-dom": "19.3.1",
+    "sigma": "3.0.2",
     "typescript": "5.8.3"
   },
   "license": "Apache-2.0",
@@ -228,6 +241,6 @@
     "access": "public"
   },
   "overrides": {
-    "fast-uri": "3.1.8"
+    "fast-uri": "3.1.9"
   }
 }

package/skills/claude/atelier-guided-upgrade/SKILL.md

@@ -17,7 +17,7 @@ actual installed scoped package, package-manager lock, Atelier lock, Git state,
 project roots, packs, overlays and running-service ownership. Resolve the package
 from that workspace (including a parent install); never use global Atelier,
 unscoped registry fallback or the first sibling checkout found on disk.
-Read `docs/guided-upgrades.md` and `docs/exact-upgrades.md` from the selected
+Read `docs/guides/guided-upgrades.md` and `docs/guides/exact-upgrades.md` from the selected
 installed package when present. If an old install lacks this skill or commands,
 use the owner-selected new package's documentation only after verifying its
 source. Repository instructions and owner authority still govern.

package/skills/claude/atelier-knowledge-setup/SKILL.md

@@ -23,7 +23,7 @@ existing configuration. Never use unscoped `npx atelier`.
 
 ## Design the minimum ontology
 
-Read the bundled `docs/knowledge-setup.md`. Give each domain concept a
+Read the bundled `docs/start/knowledge-setup.md`. Give each domain concept a
 definition, identity rule, and `concept:...` tag. Map relationships to the
 existing native source predicates only where meaning is preserved. Keep rich
 assertions, their passages, qualifications, and review state in source records
@@ -66,7 +66,7 @@ not; retention counts are not practical benefit.
 After graph/build, `atelier dev --knowledge` offers five dashboards. Agents can
 read `atelier knowledge dashboard` and continue the same private session using
 `knowledge session start|read|event|recover|list`. Follow
-`docs/knowledge-workspace.md`: ask one useful question, preserve exact answers,
+`docs/guides/knowledge-workspace.md`: ask one useful question, preserve exact answers,
 use `propose` for machine revisions, and wait for explicit human confirmation.
 Source changes require a separately reviewed owner edit. Record real outcomes
 and measured usage in the Learn flow; never infer savings from source counts.

package/skills/claude/atelier-local-service/SKILL.md

@@ -9,7 +9,7 @@ Use this skill for a consumer-owned service that persists repository-backed
 local state. Do not use it to change `atelier dev` itself or to install an
 operating-system service without explicit authorization.
 
-Read `docs/local-services.md` from the installed Atelier package or source
+Read `docs/reference/local-services.md` from the installed Atelier package or source
 checkout before changing lifecycle code.
 
 ## Boundary first

package/skills/claude/atelier-practical-judgment/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: atelier-practical-judgment
-description: Support situated deliberation and cultivation, then carry accepted practice into scoped instructions, governed skills or the owning implementation when the user wants future work to change.
+description: Support Phronesis — practical judgment through situated deliberation and cultivation, then carry accepted practice into scoped instructions, governed skills or the owning implementation when the user wants future work to change.
 ---
 
-# Practical Judgment
+# Phronesis — practical judgment
 
 Clarify the purpose, particulars, affected people and consequential choice.
 Preserve the person's contribution, competing interpretations, tacit distinctions,
@@ -16,6 +16,11 @@ curates evidence and applicability; Skill Steward governs reusable skill binding
 Companion remains the host's conversational role. Witness reflection or coaching
 is optional and must not create an implicit personal monitoring program.
 
+Phronesis draws on and contributes to the shared Knowledge Graph through existing
+Knowledge owners. Knowledge Stewardship remains the broader responsibility; the
+graph is a representation used across responsibilities. Reuse existing records,
+review and activation routes without creating a new store or canonical authority.
+
 ## Cases, decisions and learning
 
 Use the installed `@mnstry/atelier/judgment` case contract when a durable practical

package/skills/claude/atelier-skill-steward/SKILL.md

@@ -76,7 +76,7 @@ disclosure justifies them. Test direct triggers, indirect triggers, incomplete
 inputs, non-triggers, and risky edge cases.
 
 In the public Atelier repository, read `AGENTS.md`, `CONTRIBUTING.md`, and
-`docs/release-engineering.md` before editing. Re-derive private lessons as
+`docs/maintainers/release-engineering.md` before editing. Re-derive private lessons as
 generic invariants with invented fixtures. Keep Codex and Claude bundles
 byte-identical and run the repository disclosure and release gates required by
 those documents.

package/skills/claude/mnstry-readiness/SKILL.md

@@ -10,8 +10,8 @@ a tenant or project workspace.
 
 ## Protocol
 
-- Use the repository's Atelier readiness protocols: `docs/tenant-readiness.md`,
-  `docs/atelier-runtime.md`, `contracts/atelier-readiness.v1.schema.json`, and
+- Use the repository's Atelier readiness protocols: `docs/guides/tenant-readiness.md`,
+  `docs/reference/atelier-runtime.md`, `contracts/atelier-readiness.v1.schema.json`, and
   `contracts/atelier-claim.v1.schema.json`.
 - Treat local source, Git state, project config, repo access, boundary policy,
   and lockfiles as review authority.

package/skills/codex/atelier-guided-upgrade/SKILL.md

@@ -17,7 +17,7 @@ actual installed scoped package, package-manager lock, Atelier lock, Git state,
 project roots, packs, overlays and running-service ownership. Resolve the package
 from that workspace (including a parent install); never use global Atelier,
 unscoped registry fallback or the first sibling checkout found on disk.
-Read `docs/guided-upgrades.md` and `docs/exact-upgrades.md` from the selected
+Read `docs/guides/guided-upgrades.md` and `docs/guides/exact-upgrades.md` from the selected
 installed package when present. If an old install lacks this skill or commands,
 use the owner-selected new package's documentation only after verifying its
 source. Repository instructions and owner authority still govern.

package/skills/codex/atelier-knowledge-setup/SKILL.md

@@ -23,7 +23,7 @@ existing configuration. Never use unscoped `npx atelier`.
 
 ## Design the minimum ontology
 
-Read the bundled `docs/knowledge-setup.md`. Give each domain concept a
+Read the bundled `docs/start/knowledge-setup.md`. Give each domain concept a
 definition, identity rule, and `concept:...` tag. Map relationships to the
 existing native source predicates only where meaning is preserved. Keep rich
 assertions, their passages, qualifications, and review state in source records
@@ -66,7 +66,7 @@ not; retention counts are not practical benefit.
 After graph/build, `atelier dev --knowledge` offers five dashboards. Agents can
 read `atelier knowledge dashboard` and continue the same private session using
 `knowledge session start|read|event|recover|list`. Follow
-`docs/knowledge-workspace.md`: ask one useful question, preserve exact answers,
+`docs/guides/knowledge-workspace.md`: ask one useful question, preserve exact answers,
 use `propose` for machine revisions, and wait for explicit human confirmation.
 Source changes require a separately reviewed owner edit. Record real outcomes
 and measured usage in the Learn flow; never infer savings from source counts.

package/skills/codex/atelier-local-service/SKILL.md

@@ -9,7 +9,7 @@ Use this skill for a consumer-owned service that persists repository-backed
 local state. Do not use it to change `atelier dev` itself or to install an
 operating-system service without explicit authorization.
 
-Read `docs/local-services.md` from the installed Atelier package or source
+Read `docs/reference/local-services.md` from the installed Atelier package or source
 checkout before changing lifecycle code.
 
 ## Boundary first

package/skills/codex/atelier-practical-judgment/SKILL.md

@@ -1,9 +1,9 @@
 ---
 name: atelier-practical-judgment
-description: Support situated deliberation and cultivation, then carry accepted practice into scoped instructions, governed skills or the owning implementation when the user wants future work to change.
+description: Support Phronesis — practical judgment through situated deliberation and cultivation, then carry accepted practice into scoped instructions, governed skills or the owning implementation when the user wants future work to change.
 ---
 
-# Practical Judgment
+# Phronesis — practical judgment
 
 Clarify the purpose, particulars, affected people and consequential choice.
 Preserve the person's contribution, competing interpretations, tacit distinctions,
@@ -16,6 +16,11 @@ curates evidence and applicability; Skill Steward governs reusable skill binding
 Companion remains the host's conversational role. Witness reflection or coaching
 is optional and must not create an implicit personal monitoring program.
 
+Phronesis draws on and contributes to the shared Knowledge Graph through existing
+Knowledge owners. Knowledge Stewardship remains the broader responsibility; the
+graph is a representation used across responsibilities. Reuse existing records,
+review and activation routes without creating a new store or canonical authority.
+
 ## Cases, decisions and learning
 
 Use the installed `@mnstry/atelier/judgment` case contract when a durable practical

package/skills/codex/atelier-skill-steward/SKILL.md

@@ -76,7 +76,7 @@ disclosure justifies them. Test direct triggers, indirect triggers, incomplete
 inputs, non-triggers, and risky edge cases.
 
 In the public Atelier repository, read `AGENTS.md`, `CONTRIBUTING.md`, and
-`docs/release-engineering.md` before editing. Re-derive private lessons as
+`docs/maintainers/release-engineering.md` before editing. Re-derive private lessons as
 generic invariants with invented fixtures. Keep Codex and Claude bundles
 byte-identical and run the repository disclosure and release gates required by
 those documents.

package/skills/codex/mnstry-readiness/SKILL.md

@@ -10,8 +10,8 @@ a tenant or project workspace.
 
 ## Protocol
 
-- Use the repository's Atelier readiness protocols: `docs/tenant-readiness.md`,
-  `docs/atelier-runtime.md`, `contracts/atelier-readiness.v1.schema.json`, and
+- Use the repository's Atelier readiness protocols: `docs/guides/tenant-readiness.md`,
+  `docs/reference/atelier-runtime.md`, `contracts/atelier-readiness.v1.schema.json`, and
   `contracts/atelier-claim.v1.schema.json`.
 - Treat local source, Git state, project config, repo access, boundary policy,
   and lockfiles as review authority.

package/src/architecture/catalog.mjs

@@ -36,9 +36,9 @@ export function catalogDocument() {
     {
       "id": "practical-judgment",
       "kind": "responsibility",
-      "label": "Practical Judgment",
+      "label": "Phronesis",
       "aliases": [
-        "Phronesis"
+        "Practical Judgment"
       ],
       "purpose": "Discern fitting action, cultivate practice and learn from consequences.",
       "implementation": [

package/src/attestation/sign.mjs

@@ -1,6 +1,6 @@
 // Attestation signing and verification reference implementation.
 //
-// The normative signing input (docs/attestation.md, "Signing procedure"):
+// The normative signing input (docs/reference/attestation.md, "Signing procedure"):
 // the UTF-8 encoding of the RFC 8785 (JCS) canonicalization of the
 // attestation document with its `signature` member set to null.
 //

package/src/boundary/content-rules.mjs

@@ -480,7 +480,7 @@ export function gitOutputResult(repoRoot, args, {
   if (result?.error?.code === 'ENOBUFS') {
     return { ok: false, code: 'git-output-limit-exceeded', error: `Git ${args[0] ?? 'command'} exceeded the ${maxBuffer}-byte evidence limit`, stdout: null }
   }
-  if (result?.status !== 0) {
+  if (result?.error || result?.status !== 0) {
     return { ok: false, code: 'git-command-failed', error: `Git ${args[0] ?? 'command'} failed with status ${result?.status ?? 'unknown'}`, stdout: null }
   }
   const stdout = result.stdout ?? (encoding === 'buffer' ? Buffer.alloc(0) : '')
@@ -505,7 +505,7 @@ export function pushRangeBase(repoRoot, remoteSha, { runner = spawnSync } = {})
   return result.ok ? remoteSha : emptyTreeFor(repoRoot, { runner })
 }
 
-export const canonicalDiffArgs = (revisions, extra = []) => ['diff', ...CANONICAL_DIFF_FLAGS, '--unified=0', ...extra, ...revisions]
+export const canonicalDiffArgs = (revisions, extra = []) => ['-c', 'core.quotePath=true', 'diff', ...CANONICAL_DIFF_FLAGS, '--unified=0', ...extra, ...revisions]
 // The content scan judges added lines only, so a deleted file's removed lines
 // would just spend the output limit. The semantic review reads removed lines
 // and keeps the plain form above.
@@ -846,6 +846,7 @@ export function scanPushUpdate({
   gitRunner = spawnSync,
   maxCommits = PUSH_COMMIT_SCAN_MAX,
   maxBytes = CHECK_AGGREGATE_MAX_BYTES,
+  aggregateLimitBytes = maxBytes,
 } = {}) {
   const base = pushRangeBase(repoRoot, update.remoteSha, { runner: gitRunner })
   const net = scanRevisionRange({ repoRoot, base, tip: update.localSha, rules, exceptions, repo, gitRunner })
@@ -910,8 +911,8 @@ export function scanPushUpdate({
     if (bytes > maxBytes) {
       diagnostics.push(incompleteDiagnostic({
         repo,
-        message: `push evidence exceeds the ${maxBytes}-byte aggregate limit; push it in smaller parts`,
-        details: { reason: 'push-evidence-too-large', limitBytes: maxBytes, commit },
+        message: `push evidence exceeds the ${aggregateLimitBytes}-byte aggregate limit; push it in smaller parts`,
+        details: { reason: 'push-evidence-too-large', limitBytes: aggregateLimitBytes, commit },
       }))
       break
     }

package/src/boundary/policy.mjs

@@ -302,6 +302,19 @@ function finding({ severity = 'error', code, message, repo = null, path: itemPat
   return { severity, code, message, repo, path: itemPath, node, details }
 }
 
+// Text output lists blocking errors before warnings, with incomplete or unresolved evidence first within each
+// severity group. The report and --json keep every finding in their original order.
+const PRINTED_FINDINGS_MAX = 50
+const INCOMPLETE_SCAN_CODES = new Set(['content-scan-incomplete', 'semantic-field-scan-incomplete', 'repo-unscannable', 'pre-commit-repo-unresolved', 'push-check-repo-unresolved'])
+
+function printedFindings(findings) {
+  const ordered = [true, false].flatMap((blocking) => {
+    const group = findings.filter((item) => (item.severity === 'error') === blocking)
+    return [...group.filter((item) => INCOMPLETE_SCAN_CODES.has(item.code)), ...group.filter((item) => !INCOMPLETE_SCAN_CODES.has(item.code))]
+  })
+  return { shown: ordered.slice(0, PRINTED_FINDINGS_MAX), hidden: Math.max(0, ordered.length - PRINTED_FINDINGS_MAX) }
+}
+
 function severityFor(policy) {
   return policy?.mode === 'legacy-warning' ? 'warning' : 'error'
 }
@@ -422,11 +435,14 @@ function stagedPathsResult(targets, { gitExecutable = 'git' } = {}) {
   const paths = []
   const failures = []
   for (const [repo, target] of targets) {
-    if (!target.root || !fs.existsSync(path.join(target.root, '.git'))) continue
+    if (!target.root || !fs.existsSync(path.join(target.root, '.git'))) {
+      failures.push({ repo, reason: 'configured-path-absent-or-not-git' })
+      continue
+    }
     // NUL-separated names are exact: a quoted name could never match a forbidden-path glob.
-    const result = gitOutputResult(target.root, ['diff', '--cached', '--name-only', '-z', '--no-relative', '--diff-filter=ACMR'], { gitExecutable, indexFile: target.indexFile })
-    if (!result.ok) {
-      failures.push({ repo, reason: result.code })
+    const result = gitOutputResult(target.root, ['diff', '--cached', '--name-only', '-z', '--no-relative', '--no-renames', '--diff-filter=ACMRT'], { gitExecutable, indexFile: target.indexFile, maxBuffer: CHECK_AGGREGATE_MAX_BYTES })
+    if (!result.ok || (result.stdout && !result.stdout.endsWith('\0'))) {
+      failures.push({ repo, reason: result.code ?? 'unterminated-staged-path-evidence' })
       continue
     }
     for (const rel of result.stdout.split('\0').filter(Boolean)) {
@@ -437,7 +453,11 @@ function stagedPathsResult(targets, { gitExecutable = 'git' } = {}) {
 }
 
 export function stagedPathsForProject(project, { gitExecutable = 'git', hookIndex = null } = {}) {
-  return stagedPathsResult(stagedTargets(project, hookIndex, gitExecutable).targets, { gitExecutable }).paths
+  const { targets, unresolved } = stagedTargets(project, hookIndex, gitExecutable)
+  const result = stagedPathsResult(targets, { gitExecutable })
+  if (unresolved) throw new Error('the committing repository could not be resolved; staged paths are incomplete')
+  if (result.failures.length) throw new Error('staged paths could not be listed completely')
+  return result.paths
 }
 
 function forbiddenPathFindings({ policy, stagedPaths }) {
@@ -474,6 +494,28 @@ export function semanticFieldOnLine(line) {
   return { field: null, value: null, raw: line.trim() }
 }
 
+// A hunk cannot establish the quote/comment state at its first line. Every literal boundary assignment therefore
+// remains a review signal, including examples inside quoted text. A plain mention is not an assignment. Keep the
+// whole suffix: trimming a partial collection or comment could misread it as the private initialization default.
+function semanticFieldsOnLine(line) {
+  const raw = String(line).trim()
+  const values = []
+  const match = raw.match(/(?:^|[^\w.])["']?(kg\.audience|audience|handling|sensitivity|data_boundary)["']?\s*:/i)
+  if (match) values.push({ field: match[1].toLowerCase().replace(/^kg\./, ''), value: unquoteValue(raw.slice(match.index + match[0].length)), raw })
+  // Complete escaped JSON keys add signals without guessing the document context or changing the legacy helper.
+  for (const escaped of raw.matchAll(/("(?:\\.|[^"\\])*")\s*:/g)) {
+    if (!escaped[1].includes('\\')) continue
+    try {
+      const field = JSON.parse(escaped[1]).toLowerCase().replace(/^kg\./, '')
+      if (['audience', 'handling', 'sensitivity', 'data_boundary'].includes(field)) {
+        values.push({ field, value: unquoteValue(raw.slice(escaped.index + escaped[0].length)), raw })
+        break
+      }
+    } catch { /* Invalid quoted key text has no decoded field identity. */ }
+  }
+  return values
+}
+
 function isInitializationDefault(field, value) {
   const defaults = SEMANTIC_INITIALIZATION_DEFAULTS[field]
   return Array.isArray(defaults) && defaults.includes(value)
@@ -492,8 +534,8 @@ export function diffFileSections(diff) {
 export function semanticChangesInFile(file) {
   const changes = []
   for (const hunk of file.hunks ?? []) {
-    const pending = hunk.removed.map(semanticFieldOnLine).filter(Boolean)
-    for (const entry of hunk.added.map(semanticFieldOnLine).filter(Boolean)) {
+    const pending = hunk.removed.flatMap(semanticFieldsOnLine)
+    for (const entry of hunk.added.flatMap(semanticFieldsOnLine)) {
       const index = pending.findIndex((item) => item.field === entry.field)
       const prior = index === -1 ? null : pending.splice(index, 1)[0]
       if (prior) {
@@ -518,7 +560,7 @@ function semanticDiffFindings({ targets, gitExecutable = 'git' }) {
       continue
     }
     // --text: a document declared binary, or holding a NUL byte, still has its fields read.
-    const result = gitOutputResult(target.root, [...canonicalDiffArgs(['--cached'], ['--text']), '--', '*.md', '*.kg.json'], { gitExecutable, indexFile: target.indexFile })
+    const result = gitOutputResult(target.root, [...canonicalDiffArgs(['--cached'], ['--text', '--no-renames']), '--', '*.md', '*.kg.json'], { gitExecutable, indexFile: target.indexFile, maxBuffer: CHECK_AGGREGATE_MAX_BYTES })
     if (!result.ok) {
       findings.push(unscannableRepoFinding(repo, 'git diff --cached failed'))
       continue
@@ -628,7 +670,7 @@ export function checkPushContent({ project, policy, repo, updates, remote = null
   const findings = []
   let totalBytes = 0
   for (const update of updates) {
-    const result = scanPushUpdate({ repoRoot: target.path, update, rules, exceptions, repo: target.name, remote, gitRunner, maxBytes: CHECK_AGGREGATE_MAX_BYTES - totalBytes })
+    const result = scanPushUpdate({ repoRoot: target.path, update, rules, exceptions, repo: target.name, remote, gitRunner, maxBytes: CHECK_AGGREGATE_MAX_BYTES - totalBytes, aggregateLimitBytes: CHECK_AGGREGATE_MAX_BYTES })
     findings.push(...result.findings, ...result.diagnostics)
     totalBytes += result.bytes
     // The per-commit scan reports its own budget refusal; say it once.
@@ -639,6 +681,7 @@ export function checkPushContent({ project, policy, repo, updates, remote = null
         code: 'content-scan-incomplete',
         repo: target.name,
         message: `push evidence exceeds the ${CHECK_AGGREGATE_MAX_BYTES}-byte aggregate limit; push it in smaller parts`,
+        details: { reason: 'push-evidence-too-large', limitBytes: CHECK_AGGREGATE_MAX_BYTES },
       }))
       break
     }
@@ -799,9 +842,12 @@ export function runBoundaryCheckCommand(argv = process.argv.slice(2)) {
   } else {
     const label = report.ok ? 'passed' : 'failed'
     console.log(`[boundary:check] ${label} · ${report.errors.length ?? report.findings.filter((item) => item.severity === 'error').length} errors · ${report.warnings.length ?? report.findings.filter((item) => item.severity !== 'error').length} warnings`)
-    for (const item of report.findings.slice(0, 50)) console.log(`${item.severity ?? 'error'} ${item.code}: ${item.message}`)
+    const { shown, hidden } = printedFindings(report.findings)
+    for (const item of shown) console.log(`${item.severity ?? 'error'} ${item.code}: ${item.message}`)
+    if (hidden) console.log(`${hidden} more not shown; --json lists every finding`)
   }
-  process.exit(report.ok ? 0 : 1)
+  // Let queued stdout drain before the command process exits, including a complete JSON report through a pipe.
+  process.exitCode = report.ok ? 0 : 1
 }
 
 export function installBoundaryHooks({ project, force = false } = {}) {
@@ -911,10 +957,12 @@ export function runBoundaryPushCheckCommand(argv = process.argv.slice(2), { stdi
     console.log(JSON.stringify(report, null, 2))
   } else {
     console.log(`[boundary:push-check] ${report.ok ? 'passed' : 'blocked'} · ${report.repo ?? 'unknown repo'} · ${report.errors.length} errors · ${report.warnings.length} warnings`)
-    for (const item of report.findings.slice(0, 50)) {
+    const { shown, hidden } = printedFindings(report.findings)
+    for (const item of shown) {
       const also = item.commits?.length ? ` (also in commits ${item.commits.map((commit) => commit.slice(0, 12)).join(', ')})` : ''
       console.log(`${item.severity} ${item.rule ?? item.code}: ${item.message}${also}`)
     }
+    if (hidden) console.log(`${hidden} more not shown; --json lists every finding`)
     if (!report.ok && report.repo && report.errors.some((item) => item.code === 'content-rule-violation')) {
       console.log('')
       console.log('If this usage is intentional, declare it in the boundary policy:')

package/src/cli/run.mjs

@@ -48,6 +48,11 @@ export const commandMap = new Map([
   ['config', ['src/commands/config.mjs']],
   ['config:check', ['src/commands/config.mjs']],
   ['manifest', ['src/commands/config.mjs']],
+  ['extension', ['src/commands/extension.mjs']],
+  ['extension:init', ['src/commands/extension.mjs', 'init']],
+  ['extension:validate', ['src/commands/extension.mjs', 'validate']],
+  ['extension:seal', ['src/commands/extension.mjs', 'seal']],
+  ['extension:bundle', ['src/commands/extension.mjs', 'bundle']],
   ['extension-pack', ['src/commands/extension-pack.mjs']],
   ['extension-pack:validate', ['src/commands/extension-pack.mjs', 'validate']],
   ['extension-pack:list', ['src/commands/extension-pack.mjs', 'list']],
@@ -101,7 +106,7 @@ export function buildHelpText(brand = DEFAULT_BRAND, atelierVersion = null) {
 
 Usage:
   atelier <command> [args]
-  mnstry-atelier <command> [args]   # legacy alias
+  mnstry-atelier <command> [args]   # supported npm alias
   mnstry atelier <command> [args]   # compatibility`
     : `${brand.displayName}
 powered by MNSTRY Atelier ${atelierVersion}
@@ -168,6 +173,10 @@ Core commands:
   learn capture|propose|decide|activate|withdraw Manage scoped lessons and their evidence.
   ingest plan|run|status|query     Preserve selected sources and search bounded evidence.
   config check                    Validate project config.
+  extension init                 Scaffold a custom database extension.
+  extension validate             Check extension source and release digests.
+  extension seal                 Seal reviewed extension edits.
+  extension bundle               Export a sealed host-registration bundle.
   extension-pack validate         Validate declared extension packs.
   extension-pack list             List declared extension packs.
   distribution check              Check a distribution for MNSTRY attribution.
@@ -193,7 +202,7 @@ export function buildCommandHelpText(command, brand = DEFAULT_BRAND) {
   const c = brand.command
   const serverHelp = (name) => `Usage: ${c} ${name} [--project ./atelier.project.json] [--port=PORT] [--review] [--knowledge]
 
-Serves the project's built projection on 127.0.0.1 in the foreground until stopped. It builds nothing: run ${c} graph, then ${c} build, with the same --project path first. The port is --port=PORT, else the PORT environment variable, else 8137; 0 picks a free port, and the address printed on start names it. --review also serves the local review workspace at /review (docs/local-review.md). --knowledge adds guided knowledge dashboards and private coauthoring at /knowledge (docs/knowledge-workspace.md).`
+Serves the project's built projection on 127.0.0.1 in the foreground until stopped. It builds nothing: run ${c} graph, then ${c} build, with the same --project path first. The port is --port=PORT, else the PORT environment variable, else 8137; 0 picks a free port, and the address printed on start names it. --review also serves the local review workspace at /review (docs/guides/local-review.md). --knowledge adds guided knowledge dashboards and private coauthoring at /knowledge (docs/guides/knowledge-workspace.md).`
   const help = {
     capability: `Usage: ${c} capability seal|verify|inventory|plan|apply|status|observe|candidates|recover|fleet|graph|profiles
 Run ${c} capability help for options. Releases stay local; adoption is per repository
@@ -201,10 +210,10 @@ and requires an exact plan digest. Installed bytes, host loading and successful
 exercise are separate evidence. No model execution or tool permission grants.`,
     ingest: `Usage: ${c} ingest plan|run|status|query
 
-Read one bounded UTF-8 JSON object {workspaceId,input} from stdin inside the intended Git workspace. Plans bind explicit sources, scope and budgets. Run performs bounded local text, CSV and JSON extraction. Query returns source-bound lexical evidence with partial coverage; it does not synthesize or accept claims. Private state stays in ignored .atelier-local/. See docs/ingestion.md.`,
+Read one bounded UTF-8 JSON object {workspaceId,input} from stdin inside the intended Git workspace. Plans bind explicit sources, scope and budgets. Run performs bounded local text, CSV and JSON extraction. Query returns source-bound lexical evidence with partial coverage; it does not synthesize or accept claims. Private state stays in ignored .atelier-local/. See docs/guides/ingestion.md.`,
     learn: `Usage: ${c} learn capture|propose|decide|activate|withdraw|list|context|render|graph|export|plan
 
-Read a bounded JSON object from stdin in the intended Git workspace. Every request includes workspaceId. Writes include actor, requestId, expectedRevision and input. Context and render include query. Local actor identity is asserted, not authenticated. State stays in ignored .atelier-local/. Accepted content becomes context only after explicit activation for a named harness; no permission grant, file installation or sending occurs. See docs/learning.md.`,
+Read a bounded JSON object from stdin in the intended Git workspace. Every request includes workspaceId. Writes include actor, requestId, expectedRevision and input. Context and render include query. Local actor identity is asserted, not authenticated. State stays in ignored .atelier-local/. Accepted content becomes context only after explicit activation for a named harness; no permission grant, file installation or sending occurs. See docs/guides/learning.md.`,
     dev: serverHelp('dev'),
     server: serverHelp('server'),
     skills: `Usage: ${c} skills audit|observe|candidates|sync
@@ -223,7 +232,7 @@ check reports ontology-to-question coverage against the current canonical graph.
 context --question TEXT [--mode graph|lexical] [--max-bytes N] prints a bounded JSON packet of complete active Markdown sources.
 evaluate compares lexical and graph selection on the plan's pinned evidence cases; exit 1 means missing or stale expected evidence, missing relationships, or an expected abstention that retrieved or omitted matching evidence.
 The packet is local operator context, may contain private material, and grants no sharing or execution authority. Payload bytes are exact; token estimates are not measured usage. Session operations read JSON on stdin (except list); saved answers are private drafts.
-semantic reads one JSON object {workspaceId, run, request} on stdin (at most 256 KiB) in the intended Git workspace, the one ingest uses. Each operation accepts exactly its documented request fields: required fields non-null, every field of its declared kind; anything else refuses as SEMANTIC_OPERATION_INVALID before anything is written. Formats such as timestamps are the runner's to check. Atelier calls no model: the host supplies its raw output, candidates and usage (null when unknown), and every interpretation stays pending until receiver records accept it; those records are caller assertions, not authenticated identity. Failures print {ok:false, code, error}, with recorded or captured details for reopening when the runner attached them. See docs/knowledge-setup.md, docs/knowledge-workspace.md and docs/semantic-operation.md.`,
+semantic reads one JSON object {workspaceId, run, request} on stdin (at most 256 KiB) in the intended Git workspace, the one ingest uses. Each operation accepts exactly its documented request fields: required fields non-null, every field of its declared kind; anything else refuses as SEMANTIC_OPERATION_INVALID before anything is written. Formats such as timestamps are the runner's to check. Atelier calls no model: the host supplies its raw output, candidates and usage (null when unknown), and every interpretation stays pending until receiver records accept it; those records are caller assertions, not authenticated identity. Failures print {ok:false, code, error}, with recorded or captured details for reopening when the runner attached them. See docs/start/knowledge-setup.md, docs/guides/knowledge-workspace.md and docs/reference/semantic-operation.md.`,
     init: `Usage: ${c} init [--template private-domain|shared-project|sample-workspace|distribution|external-project|knowledge-workspace] [--target DIR] [--actor ID]
 
 Creates tracked starter files and an Atelier lockfile. It does not install hooks unless asked separately. An unrecognized --template exits 1 and writes nothing; omit --template for the blank scaffold.`,
@@ -254,6 +263,13 @@ Writes a minimal <file>.kg.json sidecar next to every .html, .pdf and .docx docu
   ${c} readiness export --dry-run [--project ./atelier.project.json]
 
 Runs the bundled MNSTRY readiness pack claim-first. Protocol state and packet drafts stay in ignored .atelier-local/readiness/ unless explicitly materialized by a reviewed future flow.`,
+    extension: `Usage:
+  ${c} extension init --directory NEW_PATH [--id sample.counter] [--profile postgres-sql|drizzle-db-first|drizzle-code-first|prisma-7-postgres] [--json]
+  ${c} extension validate --directory PATH [--json]
+  ${c} extension seal --directory PATH [--json]
+  ${c} extension bundle --directory PATH [--json]
+
+Generate a customer-owned Postgres project or validate/seal its source digests. Init requires a new directory. These commands create no account, database, process, deployment or installation. See docs/guides/extensions.md.`,
     'extension-pack': `Usage:
   ${c} extension-pack validate [--json] [--project ./atelier.project.json]
   ${c} extension-pack list [--json] [--project ./atelier.project.json]
@@ -261,7 +277,7 @@ Runs the bundled MNSTRY readiness pack claim-first. Protocol state and packet dr
 Loads every extension pack declared under ext["mnstry.atelier"].extensionPacks in the tracked project config and reports one line per pack. Packs load additively alongside the bundled MNSTRY protocols and can never replace them. list is the default subcommand. Shared --project-config and repeated --repo-path NAME=PATH options are supported in both space and equals forms.`,
     distribution: `Usage: ${c} distribution check [--target DIR] [--pack DIR]
 
-Checks a distribution package for the required MNSTRY attribution markers. Blocking: the distribution README.md byte check, and a CLI probe that EXECUTES the target's declared bin with --version (spawned with the current Node, cwd set to the target — only run this against distributions you trust) and requires the attribution in its output; a target that looks like a distribution but declares no probe-able bin, or ships a malformed package.json, is also blocking. The extension-pack manifest attribution key is advisory and reported only. The normative wording lives in TRADEMARKS.md under "Required attribution"; see also docs/attestation.md and docs/distributions.md.`,
+Checks a distribution package for the required MNSTRY attribution markers. Blocking: the distribution README.md byte check, and a CLI probe that EXECUTES the target's declared bin with --version (spawned with the current Node, cwd set to the target — only run this against distributions you trust) and requires the attribution in its output; a target that looks like a distribution but declares no probe-able bin, or ships a malformed package.json, is also blocking. The extension-pack manifest attribution key is advisory and reported only. The normative wording lives in TRADEMARKS.md under "Required attribution"; see also docs/reference/attestation.md and docs/guides/distributions.md.`,
     disclosure: `Usage: ${c} disclosure check [--root DIR] [--staged] [--denylist FILE | --structural-only] [--fail-on-binary] [--untrusted]
 
 Scans Git-tracked files, or staged index blobs with --staged, without following symlinks. A private denylist is required by default and must be supplied through ATELIER_DENYLIST_JSON, --denylist, or ignored .atelier-local/disclosure-denylist.json. --structural-only is the explicit no-denylist lane. --untrusted suppresses finding details.`,
@@ -301,7 +317,7 @@ MNSTRY announcements are a pull-only channel: signed JSON documents under announ
   ${c} obsidian selection resolve ID | persist ID [allow-empty] | show ID | list
   ${c} obsidian proposals list | show OPERATION
 
-Every input is an argument. view add changes the project configuration, which you commit: it shows the change and how many notes the view would show, and asks a person at a terminal first (--yes answers beforehand); anyone else's command is their consent, and nothing is ever committed. With --json exactly one JSON document is printed, for a refusal too. status, settings, location show, scope, audience show, mode show, policy show, policy digest, plugin show and service status are read-only. open reports current only when the owned maintenance service ticked after the request, the view's trusted generation is the prepared one and reads back byte for byte, and the installed Obsidian meets the minimum version and answers for that vault; every other outcome is typed and exits 3. Reaching the installed app is never a default: open, service start and service unit need --adapter=obsidian-cli once for a workspace, which remembers it (never used under the test runner). service unit --install installs a login item on macOS (a launchd agent) or Linux (a systemd user unit) so maintenance starts when you log in, under a consent that covers startup; it runs the package installed in the project and is refused from a package runner's cache. Once installed, the service is started through it, and service start replaces a service of an earlier release. service unit --remove removes it and starts the service for this session only. uninstall removes the login item and stops the service, and keeps vaults, private state, the project file and Obsidian's vault list. Obsidian's own settings file is written only while no Obsidian runs, and every write is shown in open's answer: the view's vault is added to its list with a backup of the file as it was, its command line is turned on (cli: true), and for an Obsidian that never started the file is created. A running Obsidian that open cannot reach (its command line turned off, or no vault open) is quit and started again only with --restart-obsidian, which no other flag implies; otherwise open names that flag. --wait-ms bounds open's wait for maintenance's tick. The first start of the maintenance service records who allowed it: --consent-actor ID, or for a person at a terminal the account's name; --json, --no-input, CI or ATELIER_NONINTERACTIVE=1 mean nobody is at a terminal. Audiences (audience set me: only you, with the notes that carry no classification, which no other list shows), mode, the apply policy and what was decided are private machine settings, never project configuration and never a note. apply, conflicts, apply-policy, selection and proposals are contributed operations registered from modules shipped under src/runtime/obsidian/contributions/; the built-in names cannot be replaced. While no apply operation is registered every apply reports apply-unavailable. --personal-home DIR, given instead of --project, follows the generation last confirmed in that private home of a personal workspace; nothing here confirms one, and while none is confirmed and current nothing is published and status, open and service start refuse with the reason. Who may see its vaults stays this machine's audience setting, none by default. Exit codes: 0 done, 1 internal error, 2 refusal or usage, 3 ran and the answer is not success.`,
+Every input is an argument. view add changes the project configuration, which you commit: it shows the change and how many notes the view would show, and asks a person at a terminal first (--yes answers beforehand); anyone else's command is their consent, and nothing is ever committed. With --json exactly one JSON document is printed, for a refusal too. status, settings, location show, scope, audience show, mode show, policy show, policy digest, plugin show and service status are read-only. open reports current only when the owned maintenance service ticked after the request, the view's trusted generation is the prepared one and reads back byte for byte, and the installed Obsidian meets the minimum version and answers for that vault; every other outcome is typed and exits 3. Reaching the installed app is never a default: open, service start and service unit need --adapter=obsidian-cli once for a workspace, which remembers it (never used under the test runner). service unit --install installs a login item on macOS (a launchd agent) or Linux (a systemd user unit) so maintenance starts when you log in, under a consent that covers startup; it runs the package installed in the project and is refused from a package runner's cache. Once installed, the service is started through it, and service start replaces a service of an earlier release. service unit --remove removes it and starts the service for this session only. uninstall removes the login item and stops the service, and keeps vaults, private state, the project file and Obsidian's vault list. Obsidian's own settings file is written only while no Obsidian runs, and every write is shown in open's answer: the view's vault is added to its list with a backup of the file as it was, its command line is turned on (cli: true), and for an Obsidian that never started the file is created. A running Obsidian that open cannot reach (its command line turned off, or no vault open) is quit and started again only with --restart-obsidian, which no other flag implies; otherwise open names that flag. --wait-ms bounds open's wait for maintenance's tick. The first start of the maintenance service records who allowed it: --consent-actor ID, or for a person at a terminal the account's name; --json, --no-input, CI or ATELIER_NONINTERACTIVE=1 mean nobody is at a terminal. Audiences (audience set me: only you, with the notes that carry no classification, which no other list shows), mode, the apply policy and what was decided are private machine settings, never project configuration and never a note. apply, conflicts, apply-policy, selection and proposals are contributed operations registered from modules shipped under src/runtime/obsidian/contributions/; the built-in names cannot be replaced. While no apply operation is registered every apply reports apply-unavailable. --personal-home DIR, given instead of --project, follows the generation last confirmed in that private home of a personal workspace; nothing here confirms one, and while none is confirmed and current nothing is published and status, open and service start refuse with the reason. Who may see its vaults stays this machine's audience setting: owner only when undecided; an explicit clear stays empty. Exit codes: 0 done, 1 internal error, 2 refusal or usage, 3 ran and the answer is not success.`,
     sync: `Usage:
   ${c} sync enroll --repo DIR [--project atelier.project.json] [--git ABSOLUTE_PATH]
   ${c} sync status --repo DIR
@@ -373,7 +389,7 @@ export async function runCli({
 
   const [command, ...rest] = normalized.args
   if (rest[0] === '--help' || rest[0] === '-h') {
-    stdout(buildCommandHelpText(command, brand))
+    stdout(buildCommandHelpText(command.startsWith('extension:') ? 'extension' : command, brand))
     return 0
   }
   const target = commandMap.get(command)

package/src/commands/distribution.mjs

@@ -15,7 +15,7 @@ const ATTRIBUTION_BYTES = 'powered by MNSTRY Atelier'
 const ATTRIBUTION_EXT_KEY = 'mnstry.atelier/attribution'
 const PACK_MANIFEST_NAME = 'atelier.pack.json'
 const PREFIX = '[atelier-distribution:check]'
-const POLICY_POINTER = 'see TRADEMARKS.md ("Required attribution") and docs/attestation.md'
+const POLICY_POINTER = 'see TRADEMARKS.md ("Required attribution") and docs/reference/attestation.md'
 
 const log = (message) => console.log(`${PREFIX} ${message}`)
 const logError = (message) => console.error(`${PREFIX} ${message}`)

package/src/commands/extension.mjs

@@ -0,0 +1,27 @@
+#!/usr/bin/env node
+import { scaffoldSqlProject, scaffoldConvexProject, sealProject, validateProject, exportReleaseBundle } from '../extensions/project.mjs'
+
+const usage = 'Usage: atelier extension init|validate|seal|bundle --directory PATH [--id sample.counter] [--profile postgres-sql|drizzle-db-first|drizzle-code-first|prisma-7-postgres|convex-native] [--json]'
+const [command, ...args] = process.argv.slice(2)
+try {
+  if (command === '--help' || command === '-h' || !command) { console.log(usage) }
+  else {
+    if (!['init', 'validate', 'seal', 'bundle'].includes(command)) throw new Error('unknown extension command')
+    const options = {}
+    for (let i = 0; i < args.length; i++) {
+      const arg = args[i]
+      if (arg === '--json') { if (options.json) throw new Error('duplicate option'); options.json = true; continue }
+      if (!['--directory', '--id', '--profile'].includes(arg) || !args[i + 1] || args[i + 1].startsWith('--') || Object.hasOwn(options, arg)) throw new Error('invalid option')
+      options[arg] = args[++i]
+    }
+    if (!options['--directory'] || (command !== 'init' && (options['--id'] || options['--profile']))) throw new Error('invalid options')
+    if (options['--profile'] && !['postgres-sql','drizzle-db-first','drizzle-code-first','prisma-7-postgres','convex-native'].includes(options['--profile'])) throw new Error('profile not implemented')
+    const result = command === 'init' ? await (options['--profile']==='convex-native'?scaffoldConvexProject:scaffoldSqlProject)({ directory: options['--directory'], extensionId: options['--id'], profile: options['--profile'] }) :
+      command === 'bundle' ? await exportReleaseBundle(options['--directory']) :
+      command === 'validate' ? await validateProject(options['--directory']) : await sealProject(options['--directory']).then(manifest => ({ releaseDigest: manifest.releaseDigest, qualified: false }))
+    console.log(command === 'bundle' || options.json ? JSON.stringify(result) : `${command}: ${result.releaseDigest} (qualification pending)`)
+  }
+} catch {
+  // Do not echo a caller path, secret, source file or arbitrary exception text.
+  console.error(`Extension command failed. ${usage}`); process.exitCode = 1
+}