@docyrus/docyrus 0.0.53 → 0.0.55

package/README.md

@@ -60,6 +60,7 @@ docyrus auth --help
 docyrus discover --help
 docyrus knowledge --help
 docyrus project-plan --help
+docyrus release --help
 docyrus ds --help
 docyrus apps --help
 docyrus studio --help
@@ -89,28 +90,31 @@ docyrus knowledge config --json
 
 ## Project Plan
 
-The project plan is a repo-tracked work graph stored at `docyrus/project-plan/project-plan.json`. It organizes work into sections (standalone groupings like phases or feature areas), features, and tasks. A derived `PROJECT_PLAN.md` is always kept in sync. Features are also synced into the knowledge base features document when it exists.
+The project plan is a repo-tracked work graph stored at `docyrus/project-plan/project-plan.json`. It organizes work into phases, features, and tasks. A derived `PROJECT_PLAN.md` is always kept in sync. Features are also synced into the knowledge base features document when it exists.
 
-Manage sections, features, and tasks:
+Manage phases, features, and tasks:
 
 ```bash
 docyrus project-plan show --json
 docyrus project-plan check --json
 docyrus project-plan ensure --json
+docyrus project-plan summary --json
+docyrus project-plan config --json
 
-# Sections
-docyrus project-plan upsert-section --title "Core Features" --json
-docyrus project-plan upsert-section --title "Testing" --slug "testing" --summary "Test coverage" --json
+# Phases
+docyrus project-plan upsert-phase --title "Core Features" --json
+docyrus project-plan upsert-phase --title "Testing" --slug "testing" --summary "Test coverage" --json
 
 # Features
-docyrus project-plan upsert-feature --sectionId "<section-id>" --title "Auth Flow" --json
-docyrus project-plan upsert-feature --sectionId "<section-id>" --title "Data Export" --slug "data-export" --summary "CSV and JSON export" --json
+docyrus project-plan upsert-feature --phaseId "<phase-id>" --title "Auth Flow" --json
+docyrus project-plan upsert-feature --phaseId "<phase-id>" --title "Data Export" --slug "data-export" --summary "CSV and JSON export" --json
 
 # Tasks
 docyrus project-plan upsert-task --featureId "<feature-id>" --title "Implement OAuth2" --type new-implementation --assignee agent --json
 docyrus project-plan upsert-task --featureId "<feature-id>" --title "Fix token refresh" --type bug-fix --assignee agent --status in_progress --json
 docyrus project-plan get-task --taskId "<task-id>" --json
 docyrus project-plan set-task-status --taskId "<task-id>" --status done --json
+docyrus project-plan set-order --phaseId "<phase-id>" --order 1 --json
 
 # Linked local subtasks
 docyrus project-plan create-linked-todo --taskId "<task-id>" --json
@@ -121,6 +125,22 @@ Task types: `new-implementation`, `bug-fix`, `api-test`, `browser-automation-tes
 Assignees: `agent`, `user`
 Statuses: `planned`, `in_progress`, `blocked`, `done`
 
+## Release
+
+Create versioned releases with changelog generation:
+
+```bash
+docyrus release status --json
+docyrus release new-version --json
+docyrus release new-version --bump major --json
+docyrus release new-version --version 2.0.0 --json
+docyrus release new-version --dryRun --json
+docyrus release new-version --skipChangelog --skipTag --json
+docyrus release new-version --skipGithubRelease --json
+```
+
+The `new-version` command bumps the version in `package.json`, generates a categorized changelog from commit history, creates a git tag, and optionally publishes a GitHub release via `gh`.
+
 ## Data Sources
 
 Query data source items:
@@ -240,8 +260,12 @@ docyrus server
 docyrus server --port 4000
 docyrus server --profile agent
 docyrus server --model anthropic/claude-sonnet-4-20250514 --thinking high
+docyrus server --auth "<bearer-token>"
+docyrus server --apiKey "<key>" --provider azure-openai-responses
 ```
 
+The server exposes REST endpoints for chat, models, knowledge, project-plan, release, files, and dev environment management. It also attaches a WebSocket PTY terminal at `WS /api/terminal` for interactive shell access.
+
 For full endpoint documentation see [docs/API.md](docs/API.md).
 
 ## Pi Agent and Coding Agent
@@ -274,7 +298,7 @@ When `docyrus/knowledge/` exists, `docyrus agent`, `docyrus coder`, and `docyrus
 - `docyrus_knowledge_expand`
 - `docyrus_knowledge_check`
 
-When `docyrus/project-plan/project-plan.json` exists, the `project_task` tool is also loaded with actions: `show`, `get`, `create-section`, `create-feature`, `create-task`, `set-status`, `create-linked-todo`.
+When `docyrus/project-plan/project-plan.json` exists, the agents use project-plan CLI commands (`docyrus project-plan show`, `set-task-status`, `create-linked-todo`, etc.) to read and update the canonical work graph.
 
 The `todo` tool is always available with actions: `list`, `list-all`, `get`, `create`, `update`, `append`, `delete`, `claim`, `release`.
 
@@ -287,16 +311,14 @@ Inside the interactive agent TUI:
 /logout           # remove saved provider configuration
 /plan [task]      # start a planning-only branch and keep the current plan in .docyrus/plans/
 /end-plan         # leave the planning branch, summarize it, and return to the original branch
-/architect [brief] # discover tenant data sources and generate planning artifacts under ./docyrus/architecture/
-/end-architect    # alias for leaving an architect planning session
 /plan-policy      # show the effective planning-model policy and the resolved planning model
 /read-only        # enter read-only mode — write and edit tools are disabled
 /end-read-only    # exit read-only mode and resume normal operation
-/tasks            # browse the canonical project-plan sections, features, and tasks
+/tasks            # browse the canonical project-plan phases, features, and tasks
 /todos            # interactive todo manager
 ```
 
-When running through `docyrus server`, `/plan` and `/architect` can be sent through `/api/chat` as normal chat input. If clarification is needed, the server emits a synthetic `ask_user` client tool. Frontends using AI SDK `useChat` should render that tool and submit structured answers back with `addToolOutput`.
+When running through `docyrus server`, `/plan` can be sent through `/api/chat` as normal chat input. If clarification is needed, the server emits a synthetic `ask_user` client tool. Frontends using AI SDK `useChat` should render that tool and submit structured answers back with `addToolOutput`.
 
 ### Planning-Model Policy
 

package/main.js

@@ -139349,7 +139349,7 @@ function buildInputSchema(args2, env2, options2) {
 // package.json
 var package_default = {
   name: "@docyrus/docyrus",
-  version: "0.0.53",
+  version: "0.0.55",
   private: false,
   description: "Docyrus API CLI",
   main: "./main.js",
@@ -139393,11 +139393,13 @@ var package_default = {
     unified: "^11.0.5",
     "unist-util-visit": "^5.1.0",
     "web-tree-sitter": "0.25.10",
+    ws: "^8.18.0",
     zod: "^4.3.6"
   },
   devDependencies: {
     "@types/node": "^24.12.2",
-    "@types/react": "^19.1.13"
+    "@types/react": "^19.1.13",
+    "@types/ws": "^8.5.0"
   },
   engines: {
     node: ">=22.19"
@@ -150652,12 +150654,12 @@ var import_node_child_process6 = require("node:child_process");
 var import_node_fs15 = require("node:fs");
 var import_promises18 = __toESM(require("node:fs/promises"));
 var import_node_path23 = __toESM(require("node:path"));
-function git(args2, cwd) {
-  return (0, import_node_child_process6.execFileSync)("git", args2, { cwd, encoding: "utf8", timeout: 15e3 }).trim();
+function git(args2, cwd, timeout = 15e3) {
+  return (0, import_node_child_process6.execFileSync)("git", args2, { cwd, encoding: "utf8", timeout, stdio: ["pipe", "pipe", "pipe"] }).trim();
 }
-function gitSafe(args2, cwd) {
+function gitSafe(args2, cwd, timeout) {
   try {
-    return git(args2, cwd);
+    return git(args2, cwd, timeout);
   } catch {
     return null;
   }
@@ -150796,7 +150798,13 @@ function formatEntry(commit) {
   return `${breaking}${scope}${commit.subject}`;
 }
 function detectDocyrusBackendChanges(root, sinceTag) {
-  const range = sinceTag ? `${sinceTag}..HEAD` : "HEAD~50..HEAD";
+  let range;
+  if (sinceTag) {
+    range = `${sinceTag}..HEAD`;
+  } else {
+    const rootCommit = gitSafe(["rev-list", "--max-parents=0", "HEAD"], root);
+    range = rootCommit ? `${rootCommit}..HEAD` : "HEAD";
+  }
   const entries = [];
   const diffFiles = gitSafe(["diff", "--name-only", range], root);
   if (!diffFiles) {
@@ -150950,7 +150958,7 @@ async function executeRelease(params) {
 `, "utf8");
     }
     git(["add", "-A"], root);
-    git(["commit", "-m", `chore(release): v${nextVersion}`], root);
+    git(["commit", "-m", `chore(release): v${nextVersion}`], root, 12e4);
     if (!params.skipTag) {
       git(["tag", `v${nextVersion}`], root);
     }