@agentteams/cli 0.1.22 → 0.1.23-dev.82

package/.agentteams/platform/convention-ud-guide.md

@@ -1,59 +0,0 @@
----
-trigger: -
-description: Reference when updating or deleting project conventions via the CLI.
----
-# Convention Update/Delete Guide (AgentTeams)
-
-> ⚠️ This file is automatically deployed from the server. Do not edit it directly.
-
-This guide explains how to update or delete **project convention files** using the `agentteams` CLI.
-
-## Preconditions
-
-- Update/delete only works for files produced by:
-
-~~~bash
-agentteams convention download
-~~~
-
-- Uploading arbitrary local files is not supported.
-
-## Recommended workflow
-
-1) Download conventions (also creates a local manifest used for mapping)
-
-~~~bash
-agentteams convention download
-~~~
-
-2) Edit the downloaded markdown files under `.agentteams/<category>/*.md`
-
-3) Preview changes (default: dry-run)
-
-~~~bash
-agentteams convention update --file .agentteams/rules/core-rules.md
-~~~
-
-- This prints a diff and does **not** update the server.
-
-4) Apply the update to the server
-
-~~~bash
-agentteams convention update --file .agentteams/rules/core-rules.md --apply
-~~~
-
-## Concurrency/conflict handling
-
-- The CLI prints a local diff first (dry-run by default).
-- When applying an update, the CLI sends the server's `updatedAt` value along with the request.
-- The server is authoritative and rejects the update on conflict (HTTP 409). The default policy is to stop safely.
-
-## Delete
-
-~~~bash
-# dry-run (default)
-agentteams convention delete --file .agentteams/rules/core-rules.md
-
-# apply
-agentteams convention delete --file .agentteams/rules/core-rules.md --apply
-~~~

package/.agentteams/platform/plan-guide.md

@@ -1,180 +0,0 @@
----
-trigger: model_decision
-description: Reference when creating, executing, or completing a plan.
----
-# Plan Guide (AgentTeams)
-
-> ⚠️ This file is automatically deployed from the server. Do not edit it directly.
-
-This guide defines how to **write** a high-quality plan. For execution details (status transitions, CLI commands, comments), follow your project's workflow conventions and CLI help.
-
-## What a Plan Is
-
-- A plan is a tracked unit of work with a type, status, and priority.
-- Use plans when the work spans multiple steps or requires review and verification.
-- Plans support comments, assignment, and status transitions.
-- Plans have a **type** that classifies the nature of the work:
-  - `FEATURE` — New functionality or capability
-  - `BUG_FIX` — Fix for a defect or unexpected behavior
-  - `ISSUE` — Investigation or issue resolution
-  - `REFACTOR` — Code restructuring without behavior change
-  - `CHORE` — Maintenance, config, docs, or other housekeeping
-
-## Plan Writing Workflow
-
-1. **Clarify requirements** — explore the codebase, interview the requester if needed
-2. **Write plan body** — follow Plan Tiers below to pick the right structure
-3. **Gap analysis** — SHOULD run Metis review; use the self-check below if unavailable
-4. **Register** — `agentteams plan create --file {path} --type {type} --priority {level}`
-
-Repository linkage note:
-
-- If .agentteams/config.json contains `repositoryId`, `plan create` links the new plan to that repository automatically.
-
-## Execution Shortcuts
-
-For standard execution flows, use lifecycle shortcuts instead of manual multi-step status updates.
-
-~~~bash
-# Start plan lifecycle
-agentteams plan start --id {planId}
-
-# Finish plan lifecycle
-agentteams plan finish --id {planId}
-
-# Finish and include completion report with metrics
-agentteams plan finish --id {planId} \
-  --report-title "<what you did and why, in one sentence>" \
-  --report-file .agentteams/cli/temp/{planId-first-8-chars}-report.md \
-  --quality-score <0-100, see Quality Score dimensions> \
-  --report-status <COMPLETED | PARTIAL | FAILED>
-
-~~~
-
-## Plan Start → Execution Flow
-
-When a user explicitly says to start a plan (e.g. "start plan {id}", "let's start {id}"), treat it as an explicit execution approval. Follow this flow:
-
-~~~bash
-# 1. Download runbook
-agentteams plan download --id {planId}
-
-# 2. Check for blocking comments
-agentteams comment list --plan-id {planId}
-
-# 3. Start lifecycle
-agentteams plan start --id {planId}
-~~~
-
-**Decision after comment check:**
-
-| Comments found | Action |
-|---|---|
-| `RISK` or `MODIFICATION` present | Report to user and wait for confirmation before implementing |
-| None (or `GENERAL` only) | Proceed with implementation immediately |
-
-The phrase "start the plan" is an explicit approval signal — do not stop after the CLI status change. Implement unless a blocking comment requires human confirmation.
-
-## Entity Reference Resolution
-
-Plans may contain entity references in `[label](type:id)` or `[label](type:id:path)` format. Resolve them as follows:
-
-1. **ID prefix stripping (IMPORTANT)**: The `id` part may include a type prefix such as `plan_`, `cr_`, `ca_`, `conv_`, or `pm_`. Always strip this prefix before passing the id to any CLI flag (`--id`, `--plan-id`, etc.).
-   - Example: `[My Plan](plan:plan_f62762fc-730a-4201-8586-e2541505ed1b)` → use `f62762fc-730a-4201-8586-e2541505ed1b`
-   - Full prefix list: `plan_` · `cr_` · `ca_` · `conv_` · `pm_`
-2. Resolution by type:
-   - `convention:id:.agentteams/path` → Read the local file at the given path (e.g., `.agentteams/rules/context.md`)
-   - `completionReport:id` → Download with `agentteams report download --id {id}` and read the local file
-   - `postMortem:id` → Download with `agentteams postmortem download --id {id}` and read the local file
-   - `coAction:id` → Download with `agentteams coaction download --id {id}` and read the local file
-
-## During Plan Execution
-
-Post comments to track progress:
-
-- **Risk found**: `agentteams comment create --plan-id {planId} --type RISK --content "<risk description>" --affected-files "<paths>"`
-- **Scope changed**: `agentteams comment create --plan-id {planId} --type MODIFICATION --content "<what changed and why>" --affected-files "<paths>"`
-- **Status update**: `agentteams comment create --plan-id {planId} --type GENERAL --content "<current progress>"`
-
-## After Completing or Cancelling a Plan
-
-Clean up the local runbook:
-
-~~~bash
-agentteams plan cleanup --id {planId}
-~~~
-
-## Plan Tiers — Pick the Right Level
-
-Not every plan needs the same structure. Pick the tier that matches your task size.
-
-### Minimal (1 task, 1–2 files, <30 min)
-
-- `## TL;DR` — 1–2 sentence summary, deliverables
-- `## TODOs` — What to do + Acceptance Criteria per task
-
-### Standard (2–3 tasks, known scope)
-
-Everything in Minimal, plus:
-
-- `## Context` — Original Request / Research Findings
-- `## Work Objectives` — Deliverables / Definition of Done / Must Have / Must NOT Have
-- `## Verification Strategy` — QA tool mapping (API→typecheck+test, CLI→test, Web→build)
-- TODOs add: Must NOT do / References
-
-### Full (4+ tasks, multi-wave, unfamiliar domain)
-
-Everything in Standard, plus:
-
-- Context adds: Interview Summary / Metis Review
-- `## Execution Strategy` — Parallel Waves / Dependency Matrix / Agent Dispatch
-- TODOs add: Agent Profile / Parallelization / QA Scenarios / Commit plan
-
-> When unsure, start with Standard. Upgrade to Full when tasks reach 4+.
-> `plan-template.md` provides a copyable Full-tier template. For Minimal/Standard, extract only the sections you need.
-
-## Task Required Elements
-
-Full tier requires all items. Standard tier requires ★ items only.
-
-- ★ What to do / Must NOT do
-- Recommended Agent Profile (category + skills + reason)
-- Parallelization (Wave / Blocks / Blocked By)
-- ★ References (Pattern / API / External)
-- ★ Acceptance Criteria
-- QA Scenarios (Tool / Steps / Expected Result / Evidence)
-- Commit (message + files + pre-commit)
-
-## Gap Analysis
-
-SHOULD: Ask the Metis agent to review the plan draft before registering.
-
-If Metis is unavailable, self-check:
-
-- [ ] All required sections for the chosen tier present?
-- [ ] Must NOT Have guardrails defined?
-- [ ] Each TODO has acceptance criteria?
-- [ ] Dependency graph correct (no circular blocks)?
-- [ ] File references verified to exist?
-
-## Verification Expectations
-
-- If you touched API code: run API typecheck + tests.
-- If you touched CLI code: run CLI tests.
-- If you introduced a new endpoint: add at least one request-level test.
-- If you changed a template: update its tests to match.
-
-## Common Pitfalls
-
-- Skipping tests because changes "look small"
-- Changing API contracts without updating schemas/tests
-- Writing files to project-specific directories when they should be platform-wide
-- Mixing platform content with project conventions (keep them separate)
-- Excessive comments that restate the code
-- Scope creep beyond task spec
-- Over-abstraction or premature generalization
-- Generic names (data, result, item) that obscure intent
-
-## References
-
-- `plan-template.md` — copyable Full-tier plan template

package/.agentteams/platform/plan-template.md

@@ -1,201 +0,0 @@
----
-trigger: -
-description: Copyable full plan template. Use as starting point when writing a new plan.
----
-# Plan Template (Full Tier)
-
-> ⚠️ This file is automatically deployed from the server. Do not edit it directly.
-
-> This template is for **Full tier** plans (4+ tasks, multi-wave, unfamiliar domain).
-> For Minimal or Standard plans, refer to the Plan Tiers section in `plan-guide.md` and extract only the sections you need.
-
-## TL;DR
-
-> **Quick Summary**: <!-- 1-2 sentence summary of what this plan achieves -->
->
-> **Deliverables**:
->
-> - <!-- file/module 1 — what changes -->
-> - <!-- file/module 2 — what changes -->
->
-> **Estimated Effort**: <!-- Short / Medium / Long -->
-> **Type**: <!-- FEATURE / BUG_FIX / ISSUE / REFACTOR / CHORE -->
-> **Parallel Execution**: <!-- YES / NO -->
-> **Critical Path**: <!-- Task X → Task Y → ... -->
-
----
-
-## Context
-
-### Original Request
-
-<!-- What the user/requester asked for and why -->
-
-### Interview Summary
-
-<!-- Key decisions from Q&A with the requester (if applicable) -->
-
-### Research Findings
-
-<!-- What you discovered from exploring the codebase, docs, or external sources -->
-
-### Metis Review
-
-<!-- Gaps identified by Metis review (or self-check results) -->
-
----
-
-## Work Objectives
-
-### Core Objective
-
-<!-- One sentence: what success looks like -->
-
-### Concrete Deliverables
-
-- <!-- file/module — description -->
-
-### Definition of Done
-
-- <!-- Criterion 1 -->
-- <!-- Criterion 2 -->
-
-### Must Have
-
-- <!-- Non-negotiable requirement -->
-
-### Must NOT Have (Guardrails)
-
-- <!-- Explicitly forbidden action -->
-
----
-
-## Verification Strategy
-
-> **ZERO HUMAN INTERVENTION** — ALL verification is agent-executed.
-
-### QA Policy
-
-- <!-- Tool/command mapping: API→typecheck+test, CLI→test, Web→build+playwright -->
-
----
-
-## Execution Strategy
-
-### Parallel Execution Waves
-
-~~~
-Wave 1:
-├── Task 1: description [category]
-└── Task 2: description [category]
-
-Wave 2 (Wave 1 complete):
-└── Task 3: description [category]
-~~~
-
----
-
-## TODOs
-
----
-
-- 1. Task title
-
-  **What to do**:
-
-  <!-- Detailed steps -->
-
-  **Must NOT do**:
-
-  - <!-- Forbidden action -->
-
-  **Recommended Agent Profile**:
-
-  - **Category**: `<!-- category -->`
-    - Reason: <!-- why this category -->
-  - **Skills**: <!-- skill list or none -->
-
-  **Parallelization**:
-
-  - **Can Run In Parallel**: <!-- YES / NO -->
-  - **Parallel Group**: <!-- Wave N -->
-  - **Blocks**: <!-- Task N or none -->
-  - **Blocked By**: <!-- Task N or none -->
-
-  **References**:
-
-  - <!-- file:lines — description -->
-
-  **Acceptance Criteria**:
-
-  - <!-- Verifiable criterion -->
-
-  **QA Scenarios**:
-
-  ~~~
-  Scenario: description
-    Tool: Bash
-    Steps:
-      1. command
-    Expected Result: what success looks like
-    Failure Indicators: what failure looks like
-    Evidence: .sisyphus/evidence/task-N-name.txt
-  ~~~
-
-  **Commit**: <!-- YES / NO -->
-
-  - Message: `<!-- type(scope): description -->`
-  - Files: <!-- file list -->
-  - Pre-commit: `<!-- verification command -->`
-
----
-
-## Final Verification Wave
-
-- F1. **Final check** — `quick`
-
-  1. <!-- verification command 1 -->
-  2. <!-- verification command 2 -->
-
-  Output: `<!-- result format -->`
-
----
-
-## Commit Strategy
-
-- **Task 1**: `<!-- commit message -->`
-- **Task 2**: `<!-- commit message -->`
-
-## Success Criteria
-
-~~~bash
-# <!-- description -->
-<!-- command -->
-# Expected: <!-- result -->
-~~~
-
----
-
-## QA Scenario Examples
-
-### Good (specific, verifiable)
-
-~~~
-Scenario: API returns 404 for non-existent plan
-  Tool: Bash
-  Steps:
-    1. curl -s -o /dev/null -w "%{http_code}" http://localhost:3001/api/plans/nonexistent-id
-  Expected Result: 404
-  Failure Indicators: 200 or 500
-  Evidence: .sisyphus/evidence/plan-404.txt
-~~~
-
-### Bad (vague, unverifiable)
-
-~~~
-Scenario: API works correctly
-  Tool: Manual
-  Steps:
-    1. Test the API
-  Expected Result: It works
-~~~

package/.agentteams/platform/post-mortem-guide.md

@@ -1,92 +0,0 @@
----
-trigger: model_decision
-description: Reference when writing a post mortem.
----
-# Post Mortem Guide (AgentTeams)
-
-> ⚠️ This file is automatically deployed from the server. Do not edit it directly.
-
-A post mortem is a written analysis of an incident, focusing on root cause and prevention.
-
-## Goals
-
-- Capture what happened and when
-- Identify the root cause (not symptoms)
-- Document the impact (users, revenue, SLA, operations)
-- Define concrete action items to prevent recurrence
-
-## Before You Start
-
-- Collect logs, alerts, and key timestamps.
-- Identify the affected systems and user segments.
-- Confirm whether this was a one-off or part of a recurring pattern.
-
-## Structure
-
-- Title: short incident identifier
-- Content: narrative of what happened and what was learned
-- Action items: specific tasks with owners and deadlines
-- Status: OPEN, IN_PROGRESS, or RESOLVED
-
-## Root Cause Notes
-
-- Prefer a clear causal chain over vague labels.
-- Distinguish: trigger vs contributing factors vs detection failure.
-- Include "why it was not caught earlier".
-
-## Tips
-
-- Use a clear timeline (timestamps if available)
-- Avoid blame; focus on systems and process
-- Include what detection/monitoring failed and how to improve it
-
-## Action Items
-
-- Make action items concrete and testable.
-- Prefer small items with clear ownership.
-- Track them like normal plans if they require engineering work.
-
-## Post Mortem Content Template
-
-Use this structure for the `--content` field or the `--file` content:
-
-~~~markdown
-## Summary
-<what happened — 1-2 sentences, be specific>
-
-## Timeline
-- HH:MM - <event 1>
-- HH:MM - <event 2>
-
-## Root Cause
-<specific cause, not symptoms — describe the causal chain>
-
-## Impact
-<who/what was affected and for how long>
-
-## What Went Wrong
-- <contributing factor 1>
-- <contributing factor 2>
-
-## What Went Well
-- <what helped limit the damage or speed up recovery>
-~~~
-
-## Post Mortem File Naming
-
-Use `{first 8 characters of planId}-postmortem.md`. Example: if planId is `57a51ec2-cf70-...`, the file name is `57a51ec2-postmortem.md`.
-
-## Useful Commands
-
-~~~bash
-agentteams postmortem create \
-  --plan-id {planId} \
-  --title "<what broke — e.g., 'API 500 on plan finish after schema migration'>" \
-  --file .agentteams/cli/temp/{planId-first-8-chars}-postmortem.md \
-  --action-items "<specific preventive action 1>,<specific preventive action 2>" \
-  --status OPEN
-~~~
-
-Repository linkage note:
-
-- If .agentteams/config.json contains `repositoryId`, `postmortem create` links the postmortem to that repository automatically.

package/dist/api/status.d.ts

@@ -1,12 +0,0 @@
-export declare function reportStatus(apiUrl: string, projectId: string, headers: any, body: {
-    agent: unknown;
-    status: unknown;
-    task: unknown;
-    issues: string[];
-    remaining: string[];
-}): Promise<any>;
-export declare function listStatuses(apiUrl: string, projectId: string, headers: any, params?: Record<string, number>): Promise<any>;
-export declare function getStatus(apiUrl: string, projectId: string, headers: any, id: string): Promise<any>;
-export declare function updateStatus(apiUrl: string, projectId: string, headers: any, id: string, body: Record<string, unknown>): Promise<any>;
-export declare function deleteStatus(apiUrl: string, projectId: string, headers: any, id: string): Promise<any>;
-//# sourceMappingURL=status.d.ts.map

package/dist/api/status.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"status.d.ts","sourceRoot":"","sources":["../../src/api/status.ts"],"names":[],"mappings":"AAGA,wBAAsB,YAAY,CAChC,MAAM,EAAE,MAAM,EACd,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,GAAG,EACZ,IAAI,EAAE;IACJ,KAAK,EAAE,OAAO,CAAC;IACf,MAAM,EAAE,OAAO,CAAC;IAChB,IAAI,EAAE,OAAO,CAAC;IACd,MAAM,EAAE,MAAM,EAAE,CAAC;IACjB,SAAS,EAAE,MAAM,EAAE,CAAC;CACrB,GACA,OAAO,CAAC,GAAG,CAAC,CAId;AAED,wBAAsB,YAAY,CAChC,MAAM,EAAE,MAAM,EACd,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,GAAG,EACZ,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,GAC9B,OAAO,CAAC,GAAG,CAAC,CAQd;AAED,wBAAsB,SAAS,CAC7B,MAAM,EAAE,MAAM,EACd,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,GAAG,EACZ,EAAE,EAAE,MAAM,GACT,OAAO,CAAC,GAAG,CAAC,CAId;AAED,wBAAsB,YAAY,CAChC,MAAM,EAAE,MAAM,EACd,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,GAAG,EACZ,EAAE,EAAE,MAAM,EACV,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAC5B,OAAO,CAAC,GAAG,CAAC,CAId;AAED,wBAAsB,YAAY,CAChC,MAAM,EAAE,MAAM,EACd,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,GAAG,EACZ,EAAE,EAAE,MAAM,GACT,OAAO,CAAC,GAAG,CAAC,CAMd"}

package/dist/api/status.js

@@ -1,33 +0,0 @@
-import axios from 'axios';
-import { withoutJsonContentType } from '../utils/httpHeaders.js';
-export async function reportStatus(apiUrl, projectId, headers, body) {
-    const baseUrl = `${apiUrl}/api/projects/${projectId}/agent-statuses`;
-    const response = await axios.post(baseUrl, body, { headers });
-    return response.data;
-}
-export async function listStatuses(apiUrl, projectId, headers, params) {
-    const baseUrl = `${apiUrl}/api/projects/${projectId}/agent-statuses`;
-    const requestConfig = params && Object.keys(params).length > 0
-        ? { headers, params }
-        : { headers };
-    const response = await axios.get(baseUrl, requestConfig);
-    return response.data;
-}
-export async function getStatus(apiUrl, projectId, headers, id) {
-    const baseUrl = `${apiUrl}/api/projects/${projectId}/agent-statuses`;
-    const response = await axios.get(`${baseUrl}/${id}`, { headers });
-    return response.data;
-}
-export async function updateStatus(apiUrl, projectId, headers, id, body) {
-    const baseUrl = `${apiUrl}/api/projects/${projectId}/agent-statuses`;
-    const response = await axios.put(`${baseUrl}/${id}`, body, { headers });
-    return response.data;
-}
-export async function deleteStatus(apiUrl, projectId, headers, id) {
-    const baseUrl = `${apiUrl}/api/projects/${projectId}/agent-statuses`;
-    const response = await axios.delete(`${baseUrl}/${id}`, {
-        headers: withoutJsonContentType(headers),
-    });
-    return response.data;
-}
-//# sourceMappingURL=status.js.map

package/dist/api/status.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"status.js","sourceRoot":"","sources":["../../src/api/status.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,MAAM,OAAO,CAAC;AAC1B,OAAO,EAAE,sBAAsB,EAAE,MAAM,yBAAyB,CAAC;AAEjE,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,MAAc,EACd,SAAiB,EACjB,OAAY,EACZ,IAMC;IAED,MAAM,OAAO,GAAG,GAAG,MAAM,iBAAiB,SAAS,iBAAiB,CAAC;IACrE,MAAM,QAAQ,GAAG,MAAM,KAAK,CAAC,IAAI,CAAC,OAAO,EAAE,IAAI,EAAE,EAAE,OAAO,EAAE,CAAC,CAAC;IAC9D,OAAO,QAAQ,CAAC,IAAI,CAAC;AACvB,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,MAAc,EACd,SAAiB,EACjB,OAAY,EACZ,MAA+B;IAE/B,MAAM,OAAO,GAAG,GAAG,MAAM,iBAAiB,SAAS,iBAAiB,CAAC;IACrE,MAAM,aAAa,GAAG,MAAM,IAAI,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC,MAAM,GAAG,CAAC;QAC5D,CAAC,CAAC,EAAE,OAAO,EAAE,MAAM,EAAE;QACrB,CAAC,CAAC,EAAE,OAAO,EAAE,CAAC;IAEhB,MAAM,QAAQ,GAAG,MAAM,KAAK,CAAC,GAAG,CAAC,OAAO,EAAE,aAAa,CAAC,CAAC;IACzD,OAAO,QAAQ,CAAC,IAAI,CAAC;AACvB,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,SAAS,CAC7B,MAAc,EACd,SAAiB,EACjB,OAAY,EACZ,EAAU;IAEV,MAAM,OAAO,GAAG,GAAG,MAAM,iBAAiB,SAAS,iBAAiB,CAAC;IACrE,MAAM,QAAQ,GAAG,MAAM,KAAK,CAAC,GAAG,CAAC,GAAG,OAAO,IAAI,EAAE,EAAE,EAAE,EAAE,OAAO,EAAE,CAAC,CAAC;IAClE,OAAO,QAAQ,CAAC,IAAI,CAAC;AACvB,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,MAAc,EACd,SAAiB,EACjB,OAAY,EACZ,EAAU,EACV,IAA6B;IAE7B,MAAM,OAAO,GAAG,GAAG,MAAM,iBAAiB,SAAS,iBAAiB,CAAC;IACrE,MAAM,QAAQ,GAAG,MAAM,KAAK,CAAC,GAAG,CAAC,GAAG,OAAO,IAAI,EAAE,EAAE,EAAE,IAAI,EAAE,EAAE,OAAO,EAAE,CAAC,CAAC;IACxE,OAAO,QAAQ,CAAC,IAAI,CAAC;AACvB,CAAC;AAED,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,MAAc,EACd,SAAiB,EACjB,OAAY,EACZ,EAAU;IAEV,MAAM,OAAO,GAAG,GAAG,MAAM,iBAAiB,SAAS,iBAAiB,CAAC;IACrE,MAAM,QAAQ,GAAG,MAAM,KAAK,CAAC,MAAM,CAAC,GAAG,OAAO,IAAI,EAAE,EAAE,EAAE;QACtD,OAAO,EAAE,sBAAsB,CAAC,OAAO,CAAC;KACzC,CAAC,CAAC;IACH,OAAO,QAAQ,CAAC,IAAI,CAAC;AACvB,CAAC"}

package/dist/commands/status.d.ts

@@ -1,2 +0,0 @@
-export declare function executeStatusCommand(apiUrl: string, projectId: string, headers: any, action: string, options: any): Promise<any>;
-//# sourceMappingURL=status.d.ts.map

package/dist/commands/status.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"status.d.ts","sourceRoot":"","sources":["../../src/commands/status.ts"],"names":[],"mappings":"AAGA,wBAAsB,oBAAoB,CACxC,MAAM,EAAE,MAAM,EACd,SAAS,EAAE,MAAM,EACjB,OAAO,EAAE,GAAG,EACZ,MAAM,EAAE,MAAM,EACd,OAAO,EAAE,GAAG,GACX,OAAO,CAAC,GAAG,CAAC,CA+Cd"}

package/dist/commands/status.js

@@ -1,60 +0,0 @@
-import { deleteStatus, getStatus, listStatuses, reportStatus, updateStatus } from '../api/status.js';
-import { splitCsv, toPositiveInteger } from '../utils/parsers.js';
-export async function executeStatusCommand(apiUrl, projectId, headers, action, options) {
-    switch (action) {
-        case 'report': {
-            if (!options.status)
-                throw new Error('--status is required for status report');
-            if (!options.task)
-                throw new Error('--task is required for status report');
-            if (options.issues === undefined)
-                throw new Error('--issues is required for status report');
-            if (options.remaining === undefined)
-                throw new Error('--remaining is required for status report');
-            return reportStatus(apiUrl, projectId, headers, {
-                agent: options.agent,
-                status: options.status,
-                task: options.task,
-                issues: splitCsv(options.issues),
-                remaining: splitCsv(options.remaining),
-            });
-        }
-        case 'list': {
-            const params = {};
-            const page = toPositiveInteger(options.page);
-            const pageSize = toPositiveInteger(options.pageSize);
-            if (page !== undefined)
-                params.page = page;
-            if (pageSize !== undefined)
-                params.pageSize = pageSize;
-            return listStatuses(apiUrl, projectId, headers, params);
-        }
-        case 'get': {
-            if (!options.id)
-                throw new Error('--id is required for status get');
-            return getStatus(apiUrl, projectId, headers, options.id);
-        }
-        case 'update': {
-            if (!options.id)
-                throw new Error('--id is required for status update');
-            const body = {};
-            if (options.status !== undefined)
-                body.status = options.status;
-            if (options.task !== undefined)
-                body.task = options.task;
-            if (options.issues !== undefined)
-                body.issues = splitCsv(options.issues);
-            if (options.remaining !== undefined)
-                body.remaining = splitCsv(options.remaining);
-            return updateStatus(apiUrl, projectId, headers, options.id, body);
-        }
-        case 'delete': {
-            if (!options.id)
-                throw new Error('--id is required for status delete');
-            return deleteStatus(apiUrl, projectId, headers, options.id);
-        }
-        default:
-            throw new Error(`Unknown action: ${action}`);
-    }
-}
-//# sourceMappingURL=status.js.map

package/dist/commands/status.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"status.js","sourceRoot":"","sources":["../../src/commands/status.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,YAAY,EAAE,SAAS,EAAE,YAAY,EAAE,YAAY,EAAE,YAAY,EAAE,MAAM,kBAAkB,CAAC;AACrG,OAAO,EAAE,QAAQ,EAAE,iBAAiB,EAAE,MAAM,qBAAqB,CAAC;AAElE,MAAM,CAAC,KAAK,UAAU,oBAAoB,CACxC,MAAc,EACd,SAAiB,EACjB,OAAY,EACZ,MAAc,EACd,OAAY;IAEZ,QAAQ,MAAM,EAAE,CAAC;QACf,KAAK,QAAQ,CAAC,CAAC,CAAC;YACd,IAAI,CAAC,OAAO,CAAC,MAAM;gBAAE,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;YAC/E,IAAI,CAAC,OAAO,CAAC,IAAI;gBAAE,MAAM,IAAI,KAAK,CAAC,sCAAsC,CAAC,CAAC;YAC3E,IAAI,OAAO,CAAC,MAAM,KAAK,SAAS;gBAAE,MAAM,IAAI,KAAK,CAAC,wCAAwC,CAAC,CAAC;YAC5F,IAAI,OAAO,CAAC,SAAS,KAAK,SAAS;gBAAE,MAAM,IAAI,KAAK,CAAC,2CAA2C,CAAC,CAAC;YAElG,OAAO,YAAY,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE;gBAC9C,KAAK,EAAE,OAAO,CAAC,KAAK;gBACpB,MAAM,EAAE,OAAO,CAAC,MAAM;gBACtB,IAAI,EAAE,OAAO,CAAC,IAAI;gBAClB,MAAM,EAAE,QAAQ,CAAC,OAAO,CAAC,MAAM,CAAC;gBAChC,SAAS,EAAE,QAAQ,CAAC,OAAO,CAAC,SAAS,CAAC;aACvC,CAAC,CAAC;QACL,CAAC;QACD,KAAK,MAAM,CAAC,CAAC,CAAC;YACZ,MAAM,MAAM,GAA2B,EAAE,CAAC;YAC1C,MAAM,IAAI,GAAG,iBAAiB,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;YAC7C,MAAM,QAAQ,GAAG,iBAAiB,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC;YAErD,IAAI,IAAI,KAAK,SAAS;gBAAE,MAAM,CAAC,IAAI,GAAG,IAAI,CAAC;YAC3C,IAAI,QAAQ,KAAK,SAAS;gBAAE,MAAM,CAAC,QAAQ,GAAG,QAAQ,CAAC;YAEvD,OAAO,YAAY,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,MAAM,CAAC,CAAC;QAC1D,CAAC;QACD,KAAK,KAAK,CAAC,CAAC,CAAC;YACX,IAAI,CAAC,OAAO,CAAC,EAAE;gBAAE,MAAM,IAAI,KAAK,CAAC,iCAAiC,CAAC,CAAC;YACpE,OAAO,SAAS,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,OAAO,CAAC,EAAE,CAAC,CAAC;QAC3D,CAAC;QACD,KAAK,QAAQ,CAAC,CAAC,CAAC;YACd,IAAI,CAAC,OAAO,CAAC,EAAE;gBAAE,MAAM,IAAI,KAAK,CAAC,oCAAoC,CAAC,CAAC;YACvE,MAAM,IAAI,GAA4B,EAAE,CAAC;YACzC,IAAI,OAAO,CAAC,MAAM,KAAK,SAAS;gBAAE,IAAI,CAAC,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC;YAC/D,IAAI,OAAO,CAAC,IAAI,KAAK,SAAS;gBAAE,IAAI,CAAC,IAAI,GAAG,OAAO,CAAC,IAAI,CAAC;YACzD,IAAI,OAAO,CAAC,MAAM,KAAK,SAAS;gBAAE,IAAI,CAAC,MAAM,GAAG,QAAQ,CAAC,OAAO,CAAC,MAAM,CAAC,CAAC;YACzE,IAAI,OAAO,CAAC,SAAS,KAAK,SAAS;gBAAE,IAAI,CAAC,SAAS,GAAG,QAAQ,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;YAElF,OAAO,YAAY,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,OAAO,CAAC,EAAE,EAAE,IAAI,CAAC,CAAC;QACpE,CAAC;QACD,KAAK,QAAQ,CAAC,CAAC,CAAC;YACd,IAAI,CAAC,OAAO,CAAC,EAAE;gBAAE,MAAM,IAAI,KAAK,CAAC,oCAAoC,CAAC,CAAC;YACvE,OAAO,YAAY,CAAC,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,OAAO,CAAC,EAAE,CAAC,CAAC;QAC9D,CAAC;QACD;YACE,MAAM,IAAI,KAAK,CAAC,mBAAmB,MAAM,EAAE,CAAC,CAAC;IACjD,CAAC;AACH,CAAC"}

package/dist/utils/env.d.ts

@@ -1,7 +0,0 @@
-export declare function validateEnv(): void;
-export declare function normalizeUrl(url: string): string;
-export declare function getApiConfig(): {
-    apiKey: string;
-    apiUrl: string;
-};
-//# sourceMappingURL=env.d.ts.map

package/dist/utils/env.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"env.d.ts","sourceRoot":"","sources":["../../src/utils/env.ts"],"names":[],"mappings":"AAAA,wBAAgB,WAAW,IAAI,IAAI,CAQlC;AAED,wBAAgB,YAAY,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAEhD;AAED,wBAAgB,YAAY;;;EAO3B"}