project-mgr 0.2.0 → 0.2.1

package/.env_sample

@@ -5,3 +5,6 @@
 
 # For isolated manual testing, use a separate database instead:
 # PMGR_DB_PATH=/tmp/project-mgr-manual-test.sqlite
+
+# Local Web server port.
+PORT=3000

package/README.md

@@ -178,7 +178,7 @@ Optional arguments:
 - `--status`: One of `idea`, `planned`, `active`, `blocked`, `paused`, `completed`, or `archived` (`done` is accepted as an alias for `completed`). Defaults to `completed` if omitted.
 
 - `--description`: Project introduction or description (updates project metadata).
-- `--notes`: Project notes/remarks (updates project metadata).
+- `--notes`: Persistent, medium-to-long-term project notes/remarks (e.g., architectural constraints, key caveats; updates project metadata).
 - `--progress`: Work already completed.
 - `--blocker`, `--next`, `--decision`, and `--tag`: May be specified repeatedly.
 - `--at`: When the status actually occurred. It must be an ISO 8601 timestamp with a timezone; defaults to the current time.

package/README_CN.md

@@ -178,7 +178,7 @@ pnpm start at \
 - `--status`：`idea`、`planned`、`active`、`blocked`、`paused`、`completed`、`archived` 之一（`done` 可作为 `completed` 的别名）。若省略则默认值为 `completed`。
 
 - `--description`：项目简介/描述（更新项目元数据）。
-- `--notes`：项目备注（更新项目元数据）。
+- `--notes`：中长期项目备注（如架构约束、长期备忘、关键限制等；更新项目元数据）。
 - `--progress`：已经完成的工作。
 - `--blocker`、`--next`、`--decision`、`--tag`：可以重复传入。
 - `--at`：状态实际发生时间，必须是带时区的 ISO 8601 时间；缺省为当前时间。

package/ecosystem.config.cjs

@@ -0,0 +1,21 @@
+module.exports = {
+  apps: [
+    {
+      name: "project-mgr-web",
+      cwd: __dirname,
+      script: process.execPath,
+      interpreter: "none",
+      args: [
+        "--env-file-if-exists=.env",
+        "dist/cli.js",
+        "serve",
+        "--host",
+        "127.0.0.1",
+        "--no-open",
+      ],
+      env: {
+        PMGR_DB_PATH: `${process.env.HOME}/.local/share/project-mgr/project-mgr.sqlite`,
+      },
+    },
+  ],
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "project-mgr",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Local-first append-only project status ledger",
   "type": "module",
   "bin": {

package/skills/project-mgr/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: project-mgr
-description: Manage project status with the local-first project-mgr CLI. Use when an AI agent needs to add an append-only project update, set project descriptions/notes, list or fuzzy-search projects, import status records, query current or historical project state, or export a status ledger.
+description: Manage project status with the local-first project-mgr CLI. Use when an AI agent needs to add an append-only project update, set project descriptions/notes, list or fuzzy-search projects, start the local Web Dashboard, import status records, query current or historical project state, or export a status ledger.
 ---
 
 # project-mgr
@@ -15,6 +15,15 @@ Use `npx --yes --package project-mgr pmgr`. In a source checkout, use `pnpm pmgr
 - Set `--source agent` for agent-authored updates. Use `--external-ref` only when a stable idempotency key is available.
 - If the project is not yet in the ledger database, initialize its metadata with `set-project`, backfill 3–5 historical major changes/milestones using `add` (setting appropriate historical `--at` timestamps), and then append the latest status snapshot.
 
+## Metadata vs. status entries
+
+- **Project notes (`--notes`)**: Reserved for persistent, medium-to-long-term project context (e.g., architectural constraints, permanent tech stack choices, long-term goals, or critical environment caveats).
+  - Manage notes via `set-project --project <name> --notes "..."`.
+  - **Do NOT** put transient progress, session logs, or one-off status messages into `--notes`.
+  - Avoid passing `--notes` during routine `add` commands to prevent accidentally overwriting long-term project notes.
+- **Project description (`--description`)**: A high-level, stable summary of the project's purpose.
+- **Status snapshots (`add`)**: Use `--summary` (concise milestone headline), `--progress` (detailed work accomplished), `--next` (immediate next steps), `--blocker` (current obstacles), and `--decision` for transactional, append-only updates.
+
 ## Operations
 
 Prefer `--json` for data that must be interpreted or reported programmatically.
@@ -24,14 +33,16 @@ Prefer `--json` for data that must be interpreted or reported programmatically.
 npx --yes --package project-mgr pmgr set-project --project my-project --description "Project summary" --notes "Internal notes" --json
 npx --yes --package project-mgr pmgr set-project --project my-project --clear-description --clear-notes --json
 
-
 # List all projects or fuzzy search across project names, descriptions, notes, status summaries, and tags.
 npx --yes --package project-mgr pmgr projects --json
 npx --yes --package project-mgr pmgr list --query "keyword" --json
 
+# Start the local Web Dashboard & REST API server.
+npx --yes --package project-mgr pmgr serve --port 3000 --no-open --json
+
 # Add an agent-authored status snapshot (status defaults to completed if omitted).
 npx --yes --package project-mgr pmgr add --project my-project --summary "Implemented the CLI" \
-  --description "Project description" --progress "Tests pass" --next "Publish the package" --source agent --json
+  --progress "Tests pass" --next "Publish the package" --source agent --json
 
 # Query current state, history, or state at a time.
 npx --yes --package project-mgr pmgr current --project my-project --json