loomrail 0.1.0-alpha.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,4 @@
+Loomrail
+Copyright 2026 Loomrail contributors
+
+This product includes software developed by the Loomrail project contributors.

package/README.md

@@ -0,0 +1,266 @@
+<div align="center">
+  <img src="docs/assets/brand/loomrail-wordmark.svg" alt="Loomrail" width="360" />
+  <p><strong>The local control plane for accountable AI software teams.</strong></p>
+  <p>
+    <a href="https://github.com/loomrail/loomrail/actions/workflows/ci.yml"><img src="https://github.com/loomrail/loomrail/actions/workflows/ci.yml/badge.svg" alt="CI" /></a>
+    <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-5e6ad2" alt="Apache 2.0 license" /></a>
+    <img src="https://img.shields.io/badge/status-pre--alpha-c58b20" alt="Pre-alpha status" />
+    <img src="https://img.shields.io/badge/Node.js-24.19-43853d" alt="Node.js 24.19" />
+  </p>
+</div>
+
+Loomrail is a local-first workspace for planning, running, and supervising complete software-delivery workflows
+across coding agents such as Codex and Claude Code. It is designed around tasks, evidence, budgets, review, and human
+decisions instead of disconnected chat sessions.
+
+> [!IMPORTANT]
+> Loomrail is an early pre-alpha. The local kernel, authenticated browser session, SQLite state, audit log, and
+> cross-platform CI are real. The Workbench now runs a restart-safe synthetic Discovery → Plan → Implement → Review
+> → QA → Acceptance workflow with durable budgets, evidence, Human Requests, and owner Decisions in English and
+> Russian. A live Codex session now runs inside a Git worktree cut for the task it works on, so all six stages can
+> reach a real repository; the Claude Code adapter still serves DISCOVERY, PLAN and REVIEW only.
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="docs/assets/screenshots/workbench-dark.png" />
+  <source media="(prefers-color-scheme: light)" srcset="docs/assets/screenshots/workbench-light.png" />
+  <img src="docs/assets/screenshots/workbench-light.png" alt="Loomrail Workbench with a Kanban delivery board and task inspector" width="100%" />
+</picture>
+
+## Why Loomrail
+
+- **Task-centric delivery.** Keep discovery, planning, implementation, review, QA, and acceptance on one accountable
+  route.
+- **Local by default.** The daemon binds to loopback, state lives in local SQLite, and the browser uses a one-time
+  authenticated bootstrap session.
+- **Human control.** Questions, approvals, budgets, recovery decisions, and acceptance stay visible and explicit.
+- **Auditable work.** Commands are idempotent and state changes are recorded as append-only events.
+- **Cross-platform baseline.** macOS and Windows run the same blocking verification and browser smoke tests.
+
+## Current checkpoint
+
+| Area          | Today                                                                                                                    | Next                                           |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------- |
+| Local runtime | Loopback daemon, CLI launcher, one-time browser session, installable tarball                                             | Published package and desktop installer        |
+| State         | Tasks, runs, budgets, recovery, typed evidence, acceptance packages, Decisions, append-only Events                       | Retention and restore hardening                |
+| Workbench     | Persisted board, workflow cockpit, command summary, evidence matrix, owner acceptance, EN/RU, light/dark                 | Full Attention Inbox and richer workflow views |
+| Agents        | Capability-checked provider contract, live Codex/Claude CLI adapters, per-task Git worktrees, and on-demand change diffs | The Claude Code adapter on the write path      |
+| Projects      | Bundled demo repositories, plus any local Git repository registered by absolute path                                     | Per-project guardrails and permissions         |
+| Platforms     | macOS and Windows CI are green                                                                                           | Clean-machine acceptance and hardening         |
+
+## How it is intended to work
+
+```mermaid
+flowchart LR
+  Brief[Task brief] --> Plan[Delivery plan]
+  Plan --> Build[Implementation agents]
+  Build --> Review[Independent review]
+  Review --> QA[Browser QA and evidence]
+  QA --> Accept{Human acceptance}
+  Accept -->|Approved| Done[Done]
+  Accept -->|Changes requested| Plan
+  Guardrails[Rules · permissions · budgets] -. constrain .-> Plan
+  Guardrails -. constrain .-> Build
+  Guardrails -. constrain .-> Review
+```
+
+Loomrail is the control plane around this route. It does not replace the coding agents; it gives their work a shared
+model, clear permissions, recoverable state, and an inspectable history.
+
+## Install
+
+For the complete route from installation through the first Human Request, budget decision, acceptance, live provider,
+change review, restart, and state backup, use the [English user guide](docs/guides/USER-GUIDE.md) or the
+[руководство на русском](docs/guides/USER-GUIDE.ru.md).
+
+Loomrail ships as a single package: a bundled launcher, the prebuilt Workbench, the SQLite migrations and the bundled
+fixture projects. Pre-alpha releases use the explicit `next` channel so they are never installed as a stable release:
+
+```bash
+npm install loomrail@next
+npx loomrail --port 4176
+```
+
+To verify a source revision before it reaches the registry, build and install the exact release tarball instead:
+
+```bash
+pnpm pack:release
+npm install ./dist-release/loomrail-0.1.0-alpha.1.tgz
+npx loomrail --port 4176
+```
+
+Install it globally with `npm install -g` instead if you want `loomrail` on your `PATH`. Either way the launcher
+starts on loopback and opens a one-time authenticated URL; add `--no-open` and it prints that URL instead, so a
+same-machine browser can still sign in without being opened automatically.
+
+`pnpm test:release` performs exactly this install into an empty project using only the public registry, and runs on
+macOS and Windows in CI. See the [release guide](docs/RELEASE.md) for the full procedure.
+
+## Run from source
+
+There is no desktop installer yet. To develop Loomrail, or to try the current checkpoint without building a package,
+run the repository directly.
+
+### Requirements
+
+- Node.js as pinned in [`.nvmrc`](.nvmrc)
+- Corepack
+- macOS or Windows
+
+```bash
+git clone https://github.com/loomrail/loomrail.git
+cd loomrail
+nvm use          # or: fnm use
+corepack enable  # installs the pnpm version pinned by packageManager
+pnpm install --frozen-lockfile
+pnpm dev
+```
+
+`pnpm dev` builds the workspace, starts Loomrail on an available loopback port, and opens a one-time authenticated URL
+in the default browser. Stop it with `Ctrl+C`.
+
+For a fixed port after the first build:
+
+```bash
+pnpm build
+pnpm start --port 4176
+```
+
+Use `pnpm start --no-open --port 4176` when the browser should not open automatically; the launcher then prints the
+one-time sign-in URL for a browser on the same machine. That URL signs in a single browser, expires after 60 seconds,
+and is replaced on every restart. `LOOMRAIL_DATA_DIR` can point a development run at an isolated data directory.
+
+| Platform | Default local state                                   |
+| -------- | ----------------------------------------------------- |
+| macOS    | `~/Library/Application Support/Loomrail/state.sqlite` |
+| Windows  | `%LOCALAPPDATA%\Loomrail\state.sqlite`                |
+
+## Repository
+
+```text
+apps/
+  cli/       # local launcher and authenticated browser bootstrap
+  daemon/    # loopback API, commands, events, and SQLite lifecycle
+  web/       # React Workbench
+packages/
+  contracts/             # shared schemas and transport contracts
+  domain/                # deterministic WorkItem and workflow decisions
+  persistence-sqlite/    # SQLite repositories, queue, and migrations
+  context-assembly/      # what a provider session is told, and in what order
+  workspace/             # Git process boundary, repository inspection, worktrees
+  provider-core/         # provider lifecycle and capability boundary
+  provider-mock/         # deterministic synthetic provider scenarios
+  provider-codex/        # the real `codex` CLI as a child process
+  provider-claude-code/  # the real `claude` CLI as a child process
+  workflow-engine/       # versioned workflow template validation
+  ui/                    # shared product primitives and patterns
+docs/        # product, architecture, security, design, plans, and evidence
+```
+
+The daemon owns state and capability boundaries. The web app never receives raw provider credentials and never talks
+to an agent, a shell or Git directly: every one of those crossings goes through the daemon.
+
+## Roadmap
+
+- [x] **M0 — Foundation:** monorepo, contracts, CI, public-readiness rules
+- [x] **M1 — Walking skeleton:** CLI → daemon → authenticated browser UI
+- [x] **M2 — Local kernel:** SQLite state, idempotent commands, append-only events, macOS/Windows gate
+- [x] **M3 — Real task cockpit:** authenticated API client, persisted projects/work items, editing, EN/RU, activity
+      replay and secure reconnect guidance
+- [x] **M4 — Mock delivery workflow:** restart-safe dispatch queue, Human Request, Decision, and resumable task
+      pipeline
+- [x] **M5 — Budgets and recovery:** explicit limits, pause/resume, crash recovery
+- [x] **M6 — Acceptance:** typed Review/QA evidence, criterion matrix, owner-only final approval, audit surface
+- [ ] **M7 — Public checkpoint:** packaged launcher and clean-install gate are in place; remaining work is hardening
+      and the first published release
+
+Real Codex and Claude Code execution has landed, and milestone E1 has since given it somewhere to work. Before
+dispatching a work item's first agent stage, Loomrail cuts a Git worktree for that work item on a branch of its own and
+runs the CLI there — for every stage but your own acceptance decision, because a review reads the change it judges and a
+plan is worth more when it can read the code it plans against — so **the Codex adapter now serves all six stages** under
+`codex exec -s workspace-write`. The Claude Code
+adapter still declares DISCOVERY, PLAN and REVIEW only: its write path has never been exercised against the real CLI
+here, and one adapter's evidence is not taken as proof about the other. A stage an adapter does not declare is refused
+to you as a blocking question rather than dispatched, and Loomrail never enables a permission-bypass flag on any code
+path.
+
+Your own checkout is never the working directory. Worktrees are cut under the Loomrail data directory
+(`<data>/workspaces/<project>/<work item>`), the branch is deleted only while it still is the one Loomrail cut, and a
+workspace whose directory has disappeared is reconciled at startup instead of being quietly reused.
+
+Everything downstream of the edit itself remains outside the current checkpoint: Loomrail commits nothing, pushes
+nothing and merges nothing, so a stage's work stays on its worktree's branch for you to inspect and dispose of. Plugins,
+remote mode and desktop packaging are outside it too. What comes next — project guardrails and extensibility — is
+decomposed in the [post-Phase-0 plan](docs/plans/06-post-phase-0-decomposition.ru.md).
+
+### Pointing Loomrail at a repository
+
+A Project no longer has to be one of the two bundled demos. Open **Settings → Projects**, give it the absolute path
+of a Git repository on this machine, and that repository becomes a Project you can create tasks against; the
+directory's own name becomes the project name. The path has to be absolute — a relative one would resolve against
+whatever directory the daemon happened to start in — and it has to be a repository's top level, because registering a
+subdirectory would branch the repository enclosing it without you having chosen that.
+
+Nothing stops you pointing it at this checkout, and that is deliberate. What keeps it safe is the shape of the work
+rather than a refusal: the agent writes only inside a worktree cut outside the repository, your working copy, index
+and checked-out branch are untouched, and nothing is ever pushed. Loomrail does add the worktree's bookkeeping and
+its own `loomrail/…` ref to your `.git`, and creates one commit — the carry-in snapshot that branch starts from —
+but it never moves or deletes a ref you made. Be aware of what travels with it, though — everything you have not committed is carried
+into the worktree, including untracked files the repository does not ignore, and the agent has network access in that
+same tree. The [threat model](docs/security/THREAT-MODEL.md) records this as an accepted risk rather than a solved one.
+
+Once a stage has cut one, the task card shows the workspace itself: which repository it came from, the branch, the
+base commit and the worktree path, so you can open the tree in your editor or run `git diff` against it yourself.
+
+### Choosing a provider
+
+One adapter serves every stage a daemon dispatches, for the life of the process. It is chosen by a single environment
+variable, read once at startup:
+
+| `LOOMRAIL_PROVIDER` | What runs                                                                             |
+| ------------------- | ------------------------------------------------------------------------------------- |
+| unset, or `MOCK`    | The deterministic mock adapter. No real agent runs; every stage completes on its own. |
+| `CODEX`             | The real `codex` CLI, as a child process.                                             |
+| `CLAUDE_CODE`       | The real `claude` CLI, as a child process.                                            |
+
+The values are case-sensitive. A value Loomrail cannot read falls back to `MOCK` — a typo must not stop the daemon from
+starting — but it is never silent: the launcher and the daemon log both name the value and the accepted spellings,
+because the mock completes stages successfully and you would otherwise watch a whole delivery run believing a live agent
+did it. The launcher also says when a selected adapter's CLI is not installed on this machine.
+
+The CLIs authenticate themselves: Loomrail adds nothing to the child's environment and never handles your provider
+credentials.
+
+The task card shows the files in that worktree that differ from its starting snapshot and reads one unified diff only
+when you expand that file. This is inspection, not Git authority: Loomrail still does not commit, push, or merge those
+changes.
+
+```bash
+LOOMRAIL_PROVIDER=CODEX loomrail
+```
+
+## Development
+
+```bash
+pnpm verify
+pnpm exec playwright install chromium
+pnpm test:e2e
+```
+
+`pnpm verify` runs formatting, public-tree safety checks, linting, type checks, and the test suite. Changes to the CLI,
+daemon session flow, or web shell should also pass the browser smoke test on both blocking platforms.
+
+Start with [CONTRIBUTING.md](CONTRIBUTING.md). Product and engineering sources of truth:
+
+- [Release guide](docs/RELEASE.md)
+- [Master plan](docs/product/MASTER-PLAN.ru.md)
+- [Product decisions](docs/product/PRODUCT-DECISIONS.ru.md)
+- [Architecture overview](docs/architecture/OVERVIEW.md)
+- [Phase 0 implementation plan](docs/plans/00-phase-0-implementation-plan.ru.md)
+- [Threat model](docs/security/THREAT-MODEL.md)
+- [Component system](docs/design/COMPONENT-SYSTEM.md)
+- [Brand guide](docs/design/BRAND.md)
+- [Localization contract](docs/design/LOCALIZATION.md)
+
+## License
+
+Licensed under the [Apache License 2.0](LICENSE).