@straiffi/archon 1.0.6 → 1.0.8

package/LICENSE

@@ -0,0 +1,114 @@
+Archon Package License
+
+Copyright (c) 2026 Juuso Soikkeli. All rights reserved.
+
+This Archon Package License (the "License") governs copies of the Archon software
+that are distributed by Juuso Soikkeli through the npm package `@straiffi/archon` or
+through another distribution channel expressly authorized by Juuso Soikkeli.
+
+By downloading, installing, copying, or using the Software, you agree to this
+License.
+
+1. Definitions
+
+"Licensor" means Straiffi.
+
+"Software" means the Archon software distributed under this License, including
+the package contents, bundled assets, and accompanying documentation included in
+that distribution.
+
+"You" means the individual or legal entity exercising rights under this
+License.
+
+2. License Grant
+
+Subject to your compliance with this License, Licensor grants you a limited,
+non-exclusive, non-transferable, non-sublicensable license to:
+
+- download, install, run, and use the Software for any lawful purpose, whether
+  commercial or non-commercial;
+- make copies of the Software solely as reasonably necessary for your permitted
+  use, including for backup, internal deployment, CI/CD, and internal artifact
+  caching; and
+- modify the Software and use those modified copies privately for your own use,
+  provided you do not distribute, publish, host, or otherwise make those
+  modified copies available to any third party.
+
+3. Restrictions
+
+You may not, and may not permit any third party to:
+
+- distribute, publish, transfer, assign, sublicense, sell, resell, rent,
+  lease, or otherwise make the Software available to any third party;
+- republish the Software to npm or any other package registry, mirror, or
+  public distribution channel;
+- provide, host, operate, or make the Software available as a managed service,
+  software-as-a-service, platform service, or similar offering for the benefit
+  of any third party;
+- market, offer, or provide the Software under a different brand, white-label
+  offering, OEM arrangement, or similar commercial arrangement;
+- distribute, publish, transfer, or otherwise make available any modified
+  version of the Software or any derivative work based on the Software;
+- remove or obscure any copyright, trademark, or other proprietary notice
+  included in the Software; or
+- use the Software in violation of applicable law.
+
+4. Ownership; No Source Repository Rights
+
+The Software is licensed, not sold. As between you and Licensor, Licensor and
+its licensors retain all right, title, and interest in and to the Software,
+including all intellectual property rights.
+
+This License grants no right to access, receive, or use any private source code
+repository, unpublished source code, build pipeline, or other non-public
+materials related to the Software.
+
+No trademark, trade name, logo, or brand rights are granted except as necessary
+to identify the Software as distributed by Licensor.
+
+5. Third-Party Software
+
+The Software may include or depend on third-party components that are licensed
+under separate open-source or third-party license terms. Those components are
+licensed to you under their respective terms, not this License.
+
+6. Future Versions
+
+This License applies only to the specific versions of the Software distributed
+under these terms. Licensor may release future versions of the Software under
+different terms, including paid, commercial, proprietary, or open-source terms.
+
+7. Termination
+
+This License terminates automatically if you fail to comply with any of its
+terms. Upon termination, you must stop using the Software and delete all copies
+of it in your possession or control, except to the extent applicable law
+requires otherwise.
+
+8. Disclaimer of Warranties
+
+THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTY OF ANY
+KIND, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. LICENSOR DOES
+NOT WARRANT THAT THE SOFTWARE WILL BE UNINTERRUPTED, ERROR-FREE, OR MEET YOUR
+REQUIREMENTS.
+
+9. Limitation of Liability
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL LICENSOR OR
+ITS LICENSORS BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL,
+EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, DATA,
+GOODWILL, OR BUSINESS INTERRUPTION, ARISING OUT OF OR RELATED TO THE SOFTWARE
+OR THIS LICENSE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, THE TOTAL LIABILITY OF
+LICENSOR AND ITS LICENSORS FOR ALL CLAIMS ARISING OUT OF OR RELATING TO THE
+SOFTWARE OR THIS LICENSE WILL NOT EXCEED THE AMOUNT YOU PAID LICENSOR FOR THE
+SOFTWARE IN THE TWELVE (12) MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM,
+OR TEN UNITED STATES DOLLARS (US $10.00), WHICHEVER IS GREATER.
+
+10. Entire Agreement
+
+This License is the entire agreement between you and Licensor regarding the
+Software distributed under this License, and it supersedes any prior or
+contemporaneous statements regarding that Software.

package/README.md

@@ -51,21 +51,25 @@ Required or commonly expected tools:
 | Tool | Why it matters |
 | --- | --- |
 | `git` | Required for project repositories, worktrees, diffing, and commit operations |
-| `opencode` | Required for OpenCode plan/build/chat/review workflows |
-| `claude` | Required for Claude-backed workflows |
-| `gh` | Required for GitHub PR and review integration |
+| `opencode` | Needed for OpenCode-backed plan, build, chat, and review workflows |
+| `claude` | Needed for Claude-backed workflows |
+| `gh` | Optional for GitHub PR and review workflows; GitHub API key integration also works without it |
 
-If one of the optional AI tools is missing, Archon should still start, but features that depend on that binary will return actionable errors.
+Archon should still start if an optional tool is missing, but features that depend on that binary or integration path will return actionable errors.
 
 ## How It Works
 
-Tickets move through three states:
+Archon has three main workspaces:
 
-1. **Plan**: write a title and description for the feature or task
-2. **Build**: the server spawns your configured AI tool in a new git worktree on a dedicated branch; real-time logs stream back to the UI
-3. **Review**: an agent conducts a code review and fixes any issues found
+1. **Board**: create tickets, move them through planning and implementation, and run builds in isolated git worktrees on dedicated branches.
+2. **Chat**: use persistent project chat sessions for planning, implementation help, and follow-up questions. Chat supports both planning-oriented and build-oriented turns so you can scope work first, then continue in the same conversation.
+3. **Memory**: optionally save project conventions, accepted decisions, and other prompt context in Archon so future ticket, chat, build, and review runs stay aligned with how your project works.
+
+Within the board workflow, tickets move through three stages:
 
-The frontend is a React kanban board. The backend is an Express server with a SQLite database and Socket.io for live status updates.
+1. **Plan**: write a title and description for the feature or task
+2. **Build**: Archon runs your configured AI tool in a new git worktree and streams progress back to the UI in real time
+3. **Review**: an agent reviews the resulting changes and suggests fixes that you can inspect and accept manually
 
 ## Project Setup
 
@@ -73,13 +77,13 @@ After Archon starts, create a project from the UI:
 
 1. Click `Create project`
 2. Enter a project name and repository path
-3. Optionally click `Auto-config` to inspect top-level repo files and fill any empty setup, service, or worktree sync settings
+3. Optionally click `Auto-config` to fill any empty setup, service, or worktree sync settings
 4. Optionally open `Advanced settings` to review or edit setup, service, worktree sync, and IDE settings
 5. Save the project, select it in the project switcher, and create tickets inside that project
 
 ## Project Configuration
 
-Archon stores repository and run settings per project in its database. Use the project form in the UI to configure each project.
+Use the project form in the UI to configure how Archon prepares worktrees and runs project-specific services.
 
 ### Required fields
 
@@ -88,7 +92,7 @@ Archon stores repository and run settings per project in its database. Use the p
 | `Project name` | The label shown in the project switcher, such as `Platform API` or `Marketing Site` |
 | `Repository path` | Any path inside the target git repository; Archon resolves it to the repo root before saving |
 
-`Auto-config` is available in both the create and edit project modals. It uses the currently selected global tool, reads only top-level README/config files, and fills only empty `Setup commands`, `Services`, and `Worktree sync` sections. It never changes `IDE command`.
+`Auto-config` is available in both the create and edit project modals. It fills only empty `Setup commands`, `Services`, and `Worktree sync` sections, and it never changes `IDE command`.
 
 ### Advanced fields
 
@@ -100,10 +104,6 @@ Archon stores repository and run settings per project in its database. Use the p
 | `cwd` | Optional working directory for a service, relative to the worktree root. For example, use `client` for a frontend dev server or `server` for an API process. Leave it blank to run from the worktree root. |
 | `IDE command` | Optional command to open the finished worktree in your editor after services start, such as `code --reuse-window` or `idea`. |
 
-Worktree sync entries are stored as `{ source, target?, mode }` objects. `source` is required, `target` is optional and defaults to the same path, and `mode` is either `copy` or `symlink`.
-
-Service entries are stored as `{ cmd, cwd }` objects. `cmd` is required, while `cwd` is optional.
-
 ### Example project setup
 
 ```text
@@ -143,6 +143,10 @@ Default database locations:
 
 You can override the database location with `DB_PATH`.
 
+## License
+
+Archon is distributed under the Archon Package License included with the npm package.
+
 ## Development And Maintenance
 
 - Contributor workflow: [`DEVELOPMENT.md`](https://github.com/Straiffi/Archon/blob/main/DEVELOPMENT.md)

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "@straiffi/archon",
-  "version": "1.0.6",
+  "version": "1.0.8",
   "private": false,
+  "license": "SEE LICENSE IN LICENSE",
   "type": "module",
   "workspaces": [
     "client",
@@ -12,7 +13,8 @@
   },
   "files": [
     "dist",
-    "README.md"
+    "README.md",
+    "LICENSE"
   ],
   "repository": {
     "type": "git",