@mnstry/atelier 0.2.0-alpha.1 → 0.2.0-alpha.11

package/CHANGELOG.md

@@ -1,5 +1,418 @@
 # Changelog
 
+## 0.2.0-alpha.11
+
+### Fixed
+
+- `status` now gives the same reason-specific next step as `open` for a
+  publication that stopped because an Obsidian that may hold the vault could
+  not be coordinated with (`publisher-conflict`, reason
+  `editor-uncoordinated`). The text no longer names one cause, since the
+  reason has several: another vault open, a command line that did not answer,
+  an unknown process table (on Linux, any app on a system Electron), or an app
+  started during an app-closed publication. The advice depends on whether the
+  view was ever published. Before a first publication: quit Obsidian (on
+  Linux, also any app that runs on a system Electron) so the view is
+  published, then `atelier obsidian open` starts Obsidian on it. After one:
+  the same, or open the view in the app as it is with `atelier obsidian open
+  --allow-stale`. A concurrent publisher keeps its advice.
+- The service's app qualification checks no version for an app that is not
+  running, and that answer is remembered for up to ten seconds. An editor
+  adapter built on it could coordinate with an Obsidian started inside that
+  window, whose version nobody had checked, and publish through it in-app.
+  The adapter now receives the qualification and does not coordinate, or ask
+  the app anything, unless a version was checked. An answer that checked no
+  version (the app was not running, or none was found) is no longer reused,
+  so the next publication after the app starts reads its version and
+  coordinates. A publication that stops this way is tried again on the next
+  change or at the next full reconciliation, every five minutes.
+- On macOS the app is found only at `/Applications/Obsidian.app`. An
+  Obsidian installed elsewhere is `app-missing`: nothing is published through
+  it, and publication waits while it runs. This is now documented.
+- On Linux an app started through a differently named link or launcher was
+  read as absent, because the process name is the name it was started
+  through. A process whose name is not recognised is now identified by the
+  executable `/proc/<pid>/exe` resolves to. A read failure other than a
+  process that exited or whose executable this user may not read, or a table
+  in which nothing resolves, is `unknown`.
+- The `ps` call of the process probe had no timeout, so a hung `ps` blocked
+  the service. It is killed after five seconds and the reading is `unknown`.
+- Documented that from 0.2.0-alpha.10 the app-free publication path runs in
+  production, with its re-probe window of up to two seconds plus one note
+  while Obsidian is not running (see "Known limits" in `docs/obsidian.md`).
+
+## 0.2.0-alpha.10
+
+### Fixed
+
+- A first publication refused because Obsidian runs without that vault open
+  (`publisher-conflict`, reason `editor-uncoordinated`) now advises quitting
+  Obsidian so the view publishes directly, instead of waiting for "the other
+  publisher", which does not exist.
+- The Obsidian process probe matched Atelier's own maintenance service: it
+  searched every argument of every process for an `obsidian` path segment, so
+  the service (`…/src/runtime/obsidian/service-main.mjs`) and anything naming
+  the private data root read as a running app. With the app quit, the service
+  reported `app-version-unsupported` and never published, and the app-free
+  publication path was blocked. The probe now reads `ps -A -o comm=` and
+  recognises the app by its executable: `Obsidian` and `Obsidian Helper…` on
+  macOS, `obsidian` on Linux. On Linux a system Electron process makes the
+  reading `unknown`, which is treated as a running app.
+- An app running with no vault open answers every command-line call with
+  `Vault not found.`, which was read as a version and reported as
+  `version-unknown` or `version-unreadable`. It is now the reason
+  `no-vault-open` under the existing outcome `app-version-unsupported`, still
+  not qualified, and `status` and `open` say to open any vault in Obsidian or
+  quit it. `open` waits for an app it launched that is still opening the vault.
+
+## 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
+
+- Add portable, typed advisory decision requests and results under
+  `@mnstry/atelier/decisions`, with versioned schemas, invented fixtures and
+  offline validation of evidence bindings, distributions and abstention.
+  Provider execution, credentials, budgets and authorization stay with the
+  host. See `docs/decisions.md`.
+- Add an experimental, opt-in Obsidian projection. A project that enables
+  `ext["mnstry.atelier.obsidian"]` and declares views (`full`, `scoped` or
+  `focus`, with an optional bounded expansion) gets readable, linked notes of
+  the enrolled workspace in a vault outside every repository, under private
+  per-workspace storage. Nothing is published for a project that does not
+  enable it. See `docs/obsidian.md`, `docs/obsidian-contract.md` and
+  `docs/local-services.md`.
+- Add eleven closed `atelier-obsidian-*.v1` schemas with valid and invalid
+  fixtures, each exported under its own `./contracts/` path.
+- Add deterministic materialization: note paths made of a readable title and a
+  stable identity suffix, exact byte regions that invert to their source,
+  embedded assets, and audience and eligibility rules that fail closed. No
+  audience is admitted by default, which publishes an empty view.
+- Add publication that coordinates with a running editor through conditional
+  operations, with journals, restart recovery and late-writer rechecks, so
+  that a concurrent write by a person or the app is retained rather than
+  overwritten. It depends on an atomic file exchange and is proven on macOS
+  arm64 with one app version; see the contract for what is open.
+- Add a per-workspace loopback maintenance service and the noninteractive
+  `atelier obsidian` command (`status`, `scope`, `audience`, `mode`, `policy`,
+  `service`, `open`, `apply`, `proposals`, `conflicts`, `apply-policy`,
+  `selection`). Reaching the installed app or the operating system is never a
+  default: it needs `--adapter=obsidian-cli`. The app must be version 1.13.7
+  or later.
+- Ship the selection contribution on the command: the one-line loader module
+  `src/runtime/obsidian/contributions/selection-ui.mjs` puts `selection`,
+  `conflicts` and `apply-policy` on `atelier obsidian`, beside `apply` and
+  `proposals`. The usage text names every contributed operation, and a
+  contributed operation declares under `options` which shared options it
+  takes, so `--actor` is refused everywhere but `apply run`.
+- Preserve every edit made in the vault before anything is republished. A
+  body replacement is applied to its source manually, or automatically under
+  a scoped policy the user installs and can revoke; revocation is read again
+  before every write. An edit that is not a body replacement becomes a
+  copy-only proposal in the owning repository's proposal store and is never
+  applied. Atelier makes no Git commit for any of it.
+- Add selection binding, apply-policy setup, a read-only conflict view and an
+  acceptance-receipt validator that is labelled schema validation only and
+  closes no gate.
+- Add the package subpaths `./obsidian`, `./obsidian/contracts`,
+  `./obsidian/materialize`, `./obsidian/publication`, `./obsidian/recovery`,
+  `./obsidian/edits`, `./obsidian/proposals` and `./obsidian/selection`. The
+  package root exports nothing of the projection. Names ending
+  `ForOracleTests` are test mutation controls, not a supported API.
+- `release:audit` now requires the Obsidian runtime, schemas and documents in
+  the tarball, requires every declared export to name a packed file, and
+  refuses scripts, tests, experiments, receipt directories, application
+  archives, receipts that name a real host or operator, and fixtures above 262,144
+  bytes. The path allowlist is unchanged. A package proof packs the tarball,
+  imports the subpaths from a bare consumer and publishes a synthetic
+  workspace into a temporary vault with no app.
+- Known limits: Windows refuses publication and source apply because no atomic
+  exchange is known; the real-app suite has not been run on Linux, and x86_64
+  has not been run anywhere; macOS publication needs the stock system perl;
+  the app version has a floor and no ceiling; a vault body edit to a note
+  whose source uses CRLF becomes a proposal rather than an apply. No adopter
+  acceptance is recorded.
+
+### Changed
+
+- The resolver that produces `links_to` edges is now shared by the graph and
+  the projection, and its behaviour changed in five classes. Graph artifacts a
+  consumer has committed may differ after upgrading in exactly these classes
+  and no others; each is pinned in `test/graph-knowledge-graph.test.mjs` and
+  listed in `docs/obsidian-contract.md`. Regenerate committed graph artifacts
+  after upgrading and review the difference.
+  1. Links inside fenced code (backtick or tilde, any info string, up to three
+     spaces of indent, CRLF, CommonMark fence-length rules), inside inline
+     code and inside front matter no longer produce edges. Two stray backticks
+     that happen to pair across a link count as inline code, and links after
+     an unbalanced fence that runs to the end of the file are inside code.
+  2. A link to a directory resolves to that directory's `README.md`, then
+     `index.md`, testing eligibility per candidate. A link to a parent
+     directory now resolves where the earlier reader missed it.
+  3. A link that climbs above its own repository root and re-enters through
+     the checkout's directory name is reported as leaving the enrolled roots,
+     as before. It is never turned into a repository-local edge.
+  4. Malformed percent-encoding in a link is a `link-href-malformed` finding.
+     It no longer throws out of the graph build.
+  5. The workspace graph, not repository artifacts, additionally carries
+     wikilink edges and cross-repository Markdown-link edges, de-duplicated.
+
+## 0.2.0-alpha.7
+
+- Add a guided owner-agent upgrade skill and read-only `upgrade explain`
+  reports derived from saved plans. Retain consent and provenance limits,
+  distinguish staged installation from adoption, and route unsupported
+  workspaces through their existing operator procedure.
+
+- Add explicit saved-plan local upgrade transactions with private receipts,
+  existing commit hooks and recovery inspection. Refuse unsupported Git
+  attributes before generated writes and explain abandoned preparation state.
+- `lock write` now preserves valid migration and template history and refuses
+  a malformed previous lock. Inspect and repair or separately archive the
+  invalid lock before retrying; history is no longer silently overwritten.
+
+- Add a source-only Astro reference consumer for build-time presentation tokens,
+  no-script reading/navigation, local-only form validation and cross-browser proof.
+  Keep public-page mechanics consumer-owned; add no Astro runtime dependency.
+- Patch the existing fast-uri dependency and override to 3.1.7. Clarify ordinary
+  web-link navigation versus native host navigation requests.
+
+- Validate proposed and retained adoption configurations together with their
+  policy before writing; refuse an existing default policy during blank init.
+  Compare manifests using their serialized JSON representation so omitted
+  optional fields do not make freshly generated output stale.
+- Migration: unset or correct globally exported `MNSTRY_ATELIER_ACTOR` values
+  that are not declared in the current policy. Invalid explicit selectors now
+  refuse even shared-only and legacy-warning checks.
+
+- Correct shared-only attribution so ambient platform identities cannot invent
+  an ownership requirement or trigger a network lookup. Preserve legacy-warning
+  semantics for derived identities; Sync remains strict. Match platform logins
+  only to declared logins, refuse prototype-name omissions and duplicate repos.
+- Share manifest generation between project and upgrade, store a relative graph
+  path, and compare parsed content independently of object-key order.
+- Resolve preview commands through the scoped package from root or parent installs;
+  qualify both layouts with installed health/page smoke tests. Existing preview
+  configs require an explicit user update.
+- Validate retained adoption policy/lock state before writing, refuse implicit
+  drift acceptance, detect null-digest policy drift, and refuse init collisions
+  so retries cannot overwrite authored files or reset the lock.
+
+- Repair starter document classifications, shared adoption policy validity and
+  initial adoption locks. Existing locks are retained so adoption cannot accept
+  managed-file drift implicitly.
+- Resolve template previews through the locally installed scoped package.
+- Refuse unknown or ambiguous actor declarations, prioritize platform login over
+  Git metadata, and never infer the current operator from commit history. Shared
+  policy declarations do not require ownership of private repos outside the
+  configured workspace. These checks remain attribution, not authentication.
+- Check the generated projection manifest as well as its HTML for staleness.
+
+- Add evidence-thresholded skill stewardship and exact-plan local projections;
+  refuse unmanaged collisions, managed drift and cross-workspace confirmations.
+- Add bounded immutable source copies and extraction attempt receipts, retaining
+  originals and separating byte integrity from semantic acceptance.
+- Add inert guide offers, revocable engagement and exact-payload consent contracts.
+  No remote execution, commercial authority or proprietary implementation ships.
+  See issues #33 and #34 and the skill stewardship and intake/guide documentation.
+
+- Add experimental source-bound coauthor sessions, a private draft store, JSON
+  stdin CLI and portable guided-coauthor skill. Preserve original answers,
+  confirmation, durable receipts, bounded recovery and source-change refusal;
+  no canonical source edits or publication authority are introduced.
+- Add an external-project adapter starter with declared source boundaries,
+  namespaced synthetic protocols, local-state exclusions and compatibility policy.
+- Add evidence-bound local review runs, per-claim decisions, source-owner
+  handoffs, passage responses and reading-position recovery. Current decisions
+  refuse changed evidence and stale versions; local typed names remain asserted
+  identities and no source edits are applied automatically.
+- Report installed provenance as declared origin, observed bytes or verified
+  checkout binding. Compare working bytes with commit objects, including Git
+  index hints, sanitize remote metadata, and fail exact-source checks when the
+  binding is unresolved. Piped provenance output is no longer truncated.
+- Remove unsupported numeric claim confidence and explain legacy readiness
+  scores as input completeness. Supply the required run import-safety field.
+- Add pack lifecycle qualification and dry-run migration guidance plus explicit,
+  disclosure-checked historical inspection bundles that never transfer approval.
+- Extend the existing installed consumer gate across moved source layouts,
+  durable contributions, stale refusal and inspection-only portability.
+
+## 0.2.0-alpha.6
+
+- Share project-location parsing with extension-pack commands, including
+  repeated `--repo-path NAME=PATH` overrides and both argument forms. Malformed
+  shared options now fail before local-state creation. Add path-free resolution
+  diagnostics with `config check --explain`; read boundaries remain declared
+  by the project.
+- Add Deliverable Zero for Atelier Sync: explicit single-repository
+  enrollment, a pinned direct-process Git adapter, executable repository
+  completeness observations, fast-forward-only reconciliation, per-repository
+  locking, hash-chained local operation traces, pause/resume control, and a
+  two-phase user-confirmed commit-and-publish path. No desktop shell, watcher
+  dependency, semantic conflict resolution, force operation, browser apply
+  endpoint, telemetry, or hidden upload is introduced.
+- Raise the Sync Git floor to 2.40 so default global and system attributes can
+  be observed, bind publication to the single resolved push URL, refuse URL
+  rewrite ambiguity, strip every inherited `GIT_*` process control, keep
+  read-only commands mutation-free, and return non-zero exits for paused status
+  and failed publication.
+
+## 0.2.0-alpha.5
+
+- Harden boundary enforcement so path globs use segment-aware matching, an
+  explicitly empty or malformed content-rule policy is invalid, staged and
+  pushed binary evidence is scanned within bounded budgets, incomplete Git
+  reads fail closed, linked worktrees install hooks in the correct Git common
+  directory, and `boundary audit` defaults to the current working tree with an
+  explicit `--head` snapshot mode.
+- Consolidate graph classification in one canonical engine. Markdown without a
+  `kg` block is now represented as `unclassified` with a private audience and
+  diagnostics; empty, partial, or malformed declarations remain blocking.
+  Generated projection directories remain derived from the file-class manifest
+  so graph validation and generated-only upgrade recovery cannot drift apart.
+- Bind release egress verification to the exact `npm pack` inventory, including
+  test-shaped paths that are actually published, and make the legacy egress
+  checker a thin delegate to the canonical scanner. Packed fixture-suppression
+  markers are refused and reviewed local-computed suppressions are counted.
+- Harden `atelier dev` so it binds only to loopback, requires a generated
+  `atelier.manifest.json`, serves only enrolled safe static files after
+  realpath validation, and applies host, fetch-site, origin, method, and nonce
+  checks to the relevant read and mutation routes.
+- Make collaboration records fail closed with typed corrupt-record results,
+  bounded ledger reads, POSIX no-follow and cross-platform state-leaf identity
+  validation, content-bound event identifiers, write locking, explicit
+  compaction, and one-pass proposal-list materialization. Compatibility
+  snapshots are best-effort projections of committed events rather than a
+  second authority. Proposal authority now follows declared capabilities and
+  apply endpoints rather than action-like words, and the never-released
+  provider-analysis experiment was removed before it became part of a
+  published API.
+- Render expected project and JSON failures as typed, actionable CLI messages
+  without stacks by default; set `ATELIER_DEBUG=1` to include diagnostic stacks.
+- Strengthen release proof with negative-control mutations and a bare consumer
+  that installs without publisher overrides, validates its dependency tree,
+  and imports every declared package export. A candidate is packed once, bound
+  by SHA-256, and passed unchanged through tarball audit, consumer, and branded
+  distribution gates. The trusted-publishing workflow publishes that same
+  retained, audited tarball rather than repacking the source directory.
+- Pin every JavaScript subpath and named export from `v0.2.0-alpha.4` in a
+  registry-verified compatibility baseline with immutable tag-commit and
+  public-artifact provenance. Release tooling refuses removals, provenance
+  drift, and binding modified source to an already-tagged package version.
+- Add a portable `atelier disclosure check` command that scans tracked or
+  staged consumer content, requires private denylist coverage by default, and
+  refuses tracked repository-local denylist files. Portable and repository
+  sweeps now detect the full bounded family of private-key headers and refuse
+  binary or invalid-UTF-8 evidence instead of omitting it. Fork sweeps require
+  the trusted denylist secret and cannot fall back to the untrusted checkout.
+  Repository release sweeps also inspect every bounded blob introduced by the
+  commit range, so content added and deleted before the final tree cannot
+  become public history unseen.
+- Add public agent instructions and mirrored skills for extracting reusable
+  mechanisms from private implementations without carrying tenant material
+  into Atelier, plus a managed local-service contract for durable loopback
+  authoring and review tools.
+- Document the client-zero adapter rule that exact package identity, installed
+  dependency resolution, CLI version, and `atelier.lock.json` must agree. This
+  prevents a stale sibling checkout from satisfying a current adapter proof.
+- Declare the audited `fast-uri` pin as a direct runtime dependency so packed
+  offline consumer installs resolve the same dependency closure as the source
+  checkout.
+
+## 0.2.0-alpha.4
+
+Presentation release. No contract changes and no runtime behaviour changes:
+documents valid against `0.2.0-alpha.0` remain valid.
+
+- **The README now explains the system before the package.** It begins with
+  the repository as a durable substrate, then shows how ontology, enforcement,
+  governed projections, and a local runtime make the same work usable by
+  people, teams, agents, and tools.
+- **The story progresses with the reader.** Stewards and collaborators get the
+  purpose and working loop first; builders get the graph and library surfaces;
+  technical readers retain the exact, test-gated claims, limitations, and
+  conformance boundaries.
+- **Methodology authoring is presented as the proving ground, not the
+  category.** The package can support any file-based body of work whose
+  structure, relationships, disclosure, and readiness must remain portable and
+  enforceable.
+- **Package and installation metadata match the new public presentation.** The
+  prerelease remains explicitly pinned, and the coordinated MNSTRY developer
+  documentation carries the same conceptual spine.
+- **Bundled client instructions match the released CLI.** The Codex and Claude
+  open-Atelier skills use `atelier dev` and point registry users to the scoped,
+  collision-free install path.
+
+## 0.2.0-alpha.3
+
+Documentation and metadata release. No contract changes and no runtime
+behaviour changes: documents valid against `0.2.0-alpha.0` remain valid.
+
+- **The package's promises are now under a gate.** The checkable claims,
+  the will-not-do list, the conformance/admission separation, and the
+  audience/visibility rule live canonically in `docs/blocks/`, the README
+  embeds them verbatim between markers, and a test fails when they drift.
+  Promises converge by machinery; framing diverges by audience.
+- **The README is restructured as a depth ramp** — category and trust
+  posture first, the working loop with its visible result second, the
+  checkable claims third, boundaries fourth, architecture fifth, reference
+  last — and a new "Where the Atelier stops" section states the boundary
+  with MNSTRY's managed platform as a literal table.
+- **Overbroad claims are corrected.** "Trustworthy enough for whatever you
+  govern with it" is gone from the README and `docs/design.md` — controls
+  shaped for one demanding case do not establish adequacy everywhere; the
+  agent-runtime passage now states the narrow, testable control rather
+  than a general safety claim; "does not contact external services" now
+  carries its documented `gh` exception inline; contract and test counts
+  are stated by command, not by number; the contributions text now matches
+  `CONTRIBUTING.md`'s outside-PRs-not-open-yet posture; and
+  `docs/continuity.md` speaks of npm publication in the present tense.
+- **`npx` examples use the collision-free `mnstry-atelier` form.** The
+  unscoped npm name `atelier` belongs to an unrelated third-party package,
+  so a bare `npx atelier` outside an installed workspace runs someone
+  else's code. Every `npx` example on every surface now uses the branded
+  binary, `atelier` remains the documented command inside installed
+  workspaces, and `docs/install.md` no longer calls `mnstry-atelier` a
+  legacy alias — it is the safe form.
+- **npm metadata describes the package from the outside.** A concrete
+  description, registry keywords, and a homepage that resolves to the
+  published documentation page.
+
+## 0.2.0-alpha.2
+
+Documentation and release-lane release. No contract changes and no runtime
+behaviour changes: documents valid against `0.2.0-alpha.0` remain valid.
+
+- **The README is rebuilt around the system rather than its first
+  application.** New `docs/design.md` states the design in five movements —
+  a repository with an ontology, rules that refuse, collaboration as governed
+  disclosure, a local runtime for humans and for agents, and a platform for
+  your own tool — each ending with the command that proves it. Methodology
+  authoring is stated as the first application, not the ceiling.
+- **Publishing is automated on tag push** via npm trusted publishing (OIDC),
+  so releases carry a provenance attestation and no registry token is stored
+  anywhere. Two fail-closed guards: the tagged commit must be an ancestor of
+  `main`, and the tag must equal `package.json`'s version.
+- **The disclosure scanner no longer flags the OIDC permission key.**
+  `id-token` is a GitHub Actions permission, not a credential; the exemption
+  is the literal `id-` prefix only, and every other compound still matches.
+- **`0.2.0` was published in error and unpublished the same day.** A
+  `npm version patch` against an alpha resolves the prerelease to `0.2.0`
+  rather than advancing it, and `git push --follow-tags` delivered the tag
+  even though branch protection rejected the commit, so a release published
+  from a commit that never landed on `main`. That number is permanently
+  retired on npm. The ancestry guard above exists so this cannot recur.
+
 ## 0.2.0-alpha.1
 
 First release published to the npm registry, under `@mnstry/atelier` with