@hechura/noreaster-cli 0.2.4 → 0.2.6

package/dist/commands/my-work.js

@@ -5,7 +5,7 @@ const http_1 = require("../http");
 function registerMyWorkCommands(parent) {
     parent
         .command("my-work")
-        .description("Discover assigned work items, pending reviews, open gates, and draft runs")
+        .description("Discover assigned work items, pending reviews, and open gates")
         .action(async () => {
         const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "GET", "/api/agent/my-work");
         console.log(JSON.stringify(result, null, 2));

package/dist/commands/projects.js

@@ -37,15 +37,6 @@ function registerProjectCommands(parent) {
         const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "DELETE", `/api/agent/projects/${id}`);
         console.log(JSON.stringify(result, null, 2));
     });
-    projects
-        .command("set-assignees")
-        .description("Replace project assignee ids")
-        .argument("<id>")
-        .requiredOption("--data <json>", "JSON payload with assignee_ids")
-        .action(async (id, options) => {
-        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "PUT", `/api/agent/projects/${id}/assignees`, (0, http_1.parsePayload)(options.data));
-        console.log(JSON.stringify(result, null, 2));
-    });
     projects
         .command("set-agent-assignees")
         .description("Replace project AI agent assignee ids")

package/dist/commands/reviews.js

@@ -51,14 +51,45 @@ function registerReviewCommands(parent) {
         const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "PATCH", `/api/agent/documents/${documentId}/reviews/${reviewId}`, { action: "check", item_key: itemKey, checked: !options.unchecked });
         console.log(JSON.stringify(result, null, 2));
     });
+    reviews
+        .command("comments")
+        .description("List comments and threads for a document")
+        .argument("<documentId>")
+        .action(async (documentId) => {
+        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "GET", `/api/agent/documents/${documentId}/comments`);
+        console.log(JSON.stringify(result, null, 2));
+    });
     reviews
         .command("comment")
         .description("Add a comment to a document")
         .argument("<documentId>")
         .requiredOption("--body <text>", "Comment body")
         .option("--review-id <reviewId>")
+        .option("--parent-comment-id <commentId>", "Reply to a root comment")
+        .option("--anchor-quote <text>", "Exact markdown block text to anchor")
+        .option("--anchor-block-index <index>", "Zero-based markdown block index")
         .action(async (documentId, options) => {
-        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "POST", `/api/agent/documents/${documentId}/comments`, { body: options.body, review_id: options.reviewId ?? null });
+        const hasAnchorQuote = typeof options.anchorQuote === "string";
+        const hasAnchorIndex = options.anchorBlockIndex !== undefined;
+        if (hasAnchorQuote !== hasAnchorIndex) {
+            throw new Error("--anchor-quote and --anchor-block-index must be provided together");
+        }
+        const anchorBlockIndex = hasAnchorIndex ? Number(options.anchorBlockIndex) : null;
+        if (anchorBlockIndex !== null &&
+            (!Number.isInteger(anchorBlockIndex) || anchorBlockIndex < 0)) {
+            throw new Error("--anchor-block-index must be a non-negative integer");
+        }
+        if (options.parentCommentId && (options.reviewId || hasAnchorQuote)) {
+            throw new Error("Replies cannot include --review-id or anchor options");
+        }
+        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "POST", `/api/agent/documents/${documentId}/comments`, {
+            body: options.body,
+            review_id: options.reviewId ?? null,
+            parent_comment_id: options.parentCommentId ?? null,
+            anchor: hasAnchorQuote
+                ? { quote: options.anchorQuote, blockIndex: anchorBlockIndex }
+                : null,
+        });
         console.log(JSON.stringify(result, null, 2));
     });
     reviews

package/dist/index.js

@@ -15,7 +15,6 @@ const meetings_1 = require("./commands/meetings");
 const timeline_1 = require("./commands/timeline");
 const features_1 = require("./commands/features");
 const reviews_1 = require("./commands/reviews");
-const draft_runs_1 = require("./commands/draft-runs");
 const my_work_1 = require("./commands/my-work");
 const skill_1 = require("./commands/skill");
 async function main() {
@@ -27,7 +26,6 @@ async function main() {
     (0, docs_1.registerDocumentCommands)(program);
     (0, features_1.registerFeatureCommands)(program);
     (0, reviews_1.registerReviewCommands)(program);
-    (0, draft_runs_1.registerDraftRunCommands)(program);
     (0, my_work_1.registerMyWorkCommands)(program);
     (0, skill_1.registerSkillCommands)(program);
     (0, projects_1.registerProjectCommands)(program);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hechura/noreaster-cli",
-  "version": "0.2.4",
+  "version": "0.2.6",
   "description": "CLI for Hechura Noreaster agent API access",
   "repository": {
     "type": "git",

package/skills/hechura-manager-noreaster/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hechura-manager-noreaster
-description: Operates Hechura Manager / Noreaster via the official agent CLI and PAT-scoped APIs, including the feature-spec process chain. Use when the user asks to manage Noreaster projects, tasks, sprints, customers, prospects, meetings, timeline entries, documents, features, reviews, draft runs, PR links, team/admin agent routes, or references HECHURA_AGENT_TOKEN, agent scopes, or noreaster.vercel.app docs. Also trigger for process phrases like "pick up my next work item", "submit the breakdown for review", "what gates are open", "link this PR", or "install the noreaster skill".
+description: Operates Hechura Manager / Noreaster via the official agent CLI and PAT-scoped APIs, including the feature-spec process chain. Use when the user asks to manage Noreaster projects, tasks, sprints, customers, prospects, meetings, timeline entries, documents, features, reviews, direct work-item breakdowns, PR links, team/admin agent routes, or references HECHURA_AGENT_TOKEN, agent scopes, or noreaster.vercel.app docs. Also trigger for process phrases like "pick up my next work item", "create the feature breakdown", "what gates are open", "link this PR", or "install the noreaster skill".
 ---
 
 # Hechura Manager / Noreaster Operations
@@ -10,7 +10,7 @@ Use this skill for operational work in Noreaster through the official agent CLI
 ## Execution Defaults
 
 1. Prefer the published CLI:
-   - `npx @hechura/noreaster-cli@0.2.4 <command>` or `noreaster <command>` after global install (`npm install -g @hechura/noreaster-cli@0.2.4`)
+   - `npx @hechura/noreaster-cli@0.2.6 <command>` or `noreaster <command>` after global install (`npm install -g @hechura/noreaster-cli@0.2.6`)
    - In this repo: `npm run agent -- <command>`
 2. Default API base URL:
    - `https://noreaster.vercel.app`
@@ -54,7 +54,7 @@ Ownership defaults:
 
 - PRD / Feature / Feature PRD: PM-owned
 - Feature Spec: engineering-owned
-- Work-item breakdowns: submitted by external agents as draft runs; humans review/apply
+- Work-item breakdowns: created directly by external agents; humans review the resulting items in sprint and work-item context
 - Implementation plans: authored by a developer's agent, linked to a work item
 - PRs: linked manually or via inbound webhook matching `{ticket_prefix}-<n>` (e.g. `AIM-12`)
 
@@ -65,7 +65,6 @@ Illegal transitions are refused server-side with HTTP 409 and `gate_not_satisfie
 Common gates:
 
 - Feature PRD (`feature_description`) must be approved before Feature Spec (`design_spec`) can be approved
-- Feature Spec must be approved before draft-run apply creates work items
 - Document → `approved` is a direct status transition (`docs transition <id> approved`); no approved review is required. Reviews remain available as an optional collaboration surface.
 - Agent document reads return `approved` docs by default; use `--include-drafts` only when intentionally working on drafts
 
@@ -116,6 +115,21 @@ noreaster docs update <id> --data '{"content":"...","change_summary":"Recorded d
 - Never rewrite history: use `docs revisions <id>` to inspect prior versions; corrections are new revisions, not silent replacements.
 - Content edits to an `approved` doc still record revisions. Approval itself is a human decision made by changing the document status; if your change invalidates an approval, say so explicitly rather than working around it.
 
+## Document comment threads
+
+Always list comments before replying, resolving, or adding a related comment:
+
+```bash
+noreaster reviews comments <documentId>
+```
+
+- Add a general document comment: `reviews comment <documentId> --body "Comment"`
+- Reply to a root comment: `reviews comment <documentId> --body "Reply" --parent-comment-id <commentId>`
+- Anchor a new thread to a markdown block: `reviews comment <documentId> --body "Comment" --anchor-quote "<exact block markdown>" --anchor-block-index <index>`
+- Both anchor options are required together. The index is zero-based across markdown blocks separated by blank lines; fenced code remains one block.
+- Replies inherit the root anchor and cannot include `--review-id` or anchor options.
+- Resolve the root when addressed: `reviews resolve-comment <documentId> <commentId>`.
+
 ## Work Discovery
 
 Start here when asked to pick up next work:
@@ -128,16 +142,18 @@ Returns:
 
 - assigned work items for this agent
 - open reviews for the principal owner (or unassigned open reviews)
-- features with open gates (Feature PRD approved awaiting Feature Spec; Feature Spec approved awaiting draft apply)
-- draft runs awaiting apply
+- features with open gates (Feature PRD approved awaiting Feature Spec; Feature Spec approved awaiting work items)
+
+## Creating Feature Work Items
 
-## Draft Runs
+When `my-work` reports a Feature Spec approved and awaiting work items:
 
-1. Submit breakdown: `draft-runs submit <featureId> --data '...'`
-2. Humans review in the dashboard
-3. Apply after Feature Spec approval: `draft-runs apply <featureId> <runId> [--data '...']`
+1. Read the approved Feature Spec and the project's area registry.
+2. Create each work item directly with `tasks create`.
+3. Include `feature_id`, `source_document_id`, `source_section` when applicable, `generation_method: "ai_extract"`, and the relevant `area`.
+4. Verify the created items with `tasks list --project-id <projectId>`.
 
-Do not invent silent auto-apply behavior.
+Humans review and adjust created items in sprint and work-item context; there is no intermediate review/apply step.
 
 ## NOR Short IDs and PR Linking
 
@@ -211,8 +227,7 @@ Empty `content` on create is seeded from the template for that `doc_type`.
 - `timeline`: list/get/create/update/delete
 - `docs`: list/get/create/update/transition/revisions/delete
 - `features`: list/get/create/update/transition/delete
-- `reviews`: request/approve/request-changes/check/comment/resolve-comment
-- `draft-runs`: list/get/submit/apply
+- `reviews`: request/approve/request-changes/check/comments/comment/resolve-comment
 - `messages`: list/create
 - `team`: invite/update-role/remove
 - `admin`: agents/tokens/monitoring lifecycle commands
@@ -228,11 +243,11 @@ Empty `content` on create is seeded from the template for that `doc_type`.
 ## Quick Command Examples
 
 ```bash
-npm install -g @hechura/noreaster-cli@0.2.4
+npm install -g @hechura/noreaster-cli@0.2.6
 noreaster skill install
 noreaster my-work
 noreaster features list --project-id <project-id>
-noreaster draft-runs submit <feature-id> --data '{"document_id":"<design-spec-id>","generated_items":[{"title":"Add login","type":"task","priority":"high"}]}'
+noreaster tasks create --data '{"project_id":"<project-id>","feature_id":"<feature-id>","source_document_id":"<design-spec-id>","generation_method":"ai_extract","title":"[BE - api] Add login","type":"task","priority":"high","area":"be-api"}'
 noreaster tasks pr-link <task-id> --url 'https://github.com/owner/repo/pull/12'
 ```
 

package/dist/commands/draft-runs.js

@@ -1,44 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.registerDraftRunCommands = registerDraftRunCommands;
-const http_1 = require("../http");
-function registerDraftRunCommands(parent) {
-    const draftRuns = parent.command("draft-runs").description("Manage external draft work-item runs");
-    draftRuns
-        .command("list")
-        .description("List draft runs for a feature")
-        .argument("<featureId>")
-        .action(async (featureId) => {
-        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "GET", `/api/agent/features/${featureId}/draft-runs`);
-        console.log(JSON.stringify(result, null, 2));
-    });
-    draftRuns
-        .command("get")
-        .description("Get a draft run")
-        .argument("<featureId>")
-        .argument("<runId>")
-        .action(async (featureId, runId) => {
-        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "GET", `/api/agent/features/${featureId}/draft-runs/${runId}`);
-        console.log(JSON.stringify(result, null, 2));
-    });
-    draftRuns
-        .command("submit")
-        .description("Submit a draft run for a feature")
-        .argument("<featureId>")
-        .requiredOption("--data <json>", "JSON payload with source_document_id and items")
-        .action(async (featureId, options) => {
-        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "POST", `/api/agent/features/${featureId}/draft-runs`, (0, http_1.parsePayload)(options.data));
-        console.log(JSON.stringify(result, null, 2));
-    });
-    draftRuns
-        .command("apply")
-        .description("Apply a draft run (creates work items)")
-        .argument("<featureId>")
-        .argument("<runId>")
-        .option("--data <json>", "Optional edited items payload")
-        .action(async (featureId, runId, options) => {
-        const payload = options.data ? (0, http_1.parsePayload)(options.data) : {};
-        const result = await (0, http_1.apiRequest)((0, http_1.resolveConfig)(), "POST", `/api/agent/features/${featureId}/draft-runs/${runId}/apply`, payload);
-        console.log(JSON.stringify(result, null, 2));
-    });
-}