@iamu-dev/iamu 0.8.0-beta.2 → 0.8.0-beta.4

package/README.md

@@ -28,7 +28,7 @@ In the root of your project:
 npx @iamu-dev/iamu@beta init
 ```
 
-`iamu init` scaffolds the `iamu/` directory and configures skills for your editor (Claude Code, Cursor, Windsurf, Cline, Codex, RooCode).
+`iamu init` scaffolds the `iamu/` directory and configures skills for your editor (Claude Code, Cursor, Windsurf, GitHub Copilot, Cline, Codex, RooCode, Antigravity).
 
 ## Core Commands
 
@@ -38,10 +38,15 @@ npx @iamu-dev/iamu@beta init
 |---------|-------------|
 | `iamu init [--yes] [--json]` | Initialize or configure an iamu project in current workspace |
 | `iamu status [--json]` | Overview of personas, scenarios, active runs, and cloud sync status |
-| `iamu doctor` | Diagnose directory structure, schemas, and missing dependencies |
+| `iamu doctor [-t <url>] [--json]` | Diagnose directory structure, schemas, and missing dependencies |
+| `iamu preflight [--cwd <path>] [--json]` | Fast typecheck verification before walkthroughs |
 | `iamu list [type] [--capability <slug>] [--json [fields]]` | List personas, scenarios, findings, capabilities, or outlines |
+| `iamu new <type> [--name <name>] [--slug <slug>]` | Create a new entity (persona, outline, scenario, source, capability) |
+| `iamu set <type> [slug]` | Set fields or configuration on existing entities |
+| `iamu edit <type> [slug]` | Interactively edit an entity or context configuration |
+| `iamu explore` / `iamu explore run [url]` | Map the running product with a read-only crawl, and compare maps with runs |
 | `iamu validate [path] [--all]` | Validate entity files against protocol schemas |
-| `iamu update` | Refresh installed editor agent skills to latest templates |
+| `iamu update [--host <name>]` | Refresh installed editor agent skills to latest templates |
 
 ### Walkthrough Execution Loop
 
@@ -57,18 +62,41 @@ start-run → instructions walk → browse step / step, new-finding, summary
 | `iamu browse <command> [args]` | Control Google Chrome via CDP (start, goto, click, fill, shot, snapshot) |
 | `iamu step [run-id] --action "..."` | Record a walkthrough step atomically into `steps/` and `screenshots/` |
 | `iamu new-finding [run-id]` | Scaffold a new finding markdown file with valid UUID and frontmatter |
+| `iamu summary [run-id] [--json]` | Record closing synthesis or early blocker reason |
 | `iamu complete <run-id> [--json]` | Assemble canonical report, evaluate provenance, and mirror to cloud |
 | `iamu match <run-id>` | Generate matching prompt to link findings to prior runs |
 | `iamu match-record <run-id> --file <path> [--json]` | Record matcher resolutions and re-derive run delta |
 | `iamu evaluate <run-id> [--json]` | Compose evaluation prompt for human-test questions |
 | `iamu evaluate-record <run-id> --file <path> [--json]` | Record evaluation verdicts into `verdicts.json` |
+| `iamu advise [run-id] [--json]` | Compose technical advisor prompt for code-level recommendations |
+| `iamu advise-record [run-id] [--file <path>] [--json]` | Record accepted recommendations and systemic directions |
+| `iamu designer <run-id> [--json]` | Compose design review prompt comparing screens to design docs |
+| `iamu designer-record <run-id> [--file <path>] [--json]` | Record designer review findings and rule evaluations |
+| `iamu designer-dismiss <run-id> <finding>` | Dismiss a designer finding (D<n>) from a run's designer review |
+| `iamu directions [set <slug>]` | List structural changes proposed by the advisor, or update direction status |
+| `iamu fix-brief [finding]` | Synthesize concrete remediation brief from finding and directions |
+
+### Design & Review
+
+| Command | Description |
+|---------|-------------|
+| `iamu design status [--json]` | Check recorded design docs, rules cited, and open proposals |
+| `iamu design detect [--record] [--json]` | Detect design docs, CSS/tokens, and component systems in repo |
+| `iamu design sources <paths...> [--kind <kind>] [--applies-to <list>]` | Record files or headings as authoritative design references |
+| `iamu design review <target> [--json]` | Compose design review prompt for a specific page or route |
+| `iamu design review-record <target> [--file <path>] [--json]` | Record design review answers for a reviewed page |
+| `iamu design review-match <target> [--json]` | Write prompt to check earlier designer findings after a page review |
+| `iamu design review-match-record <target> [--file <path>] [--json]` | Record match answer indicating which earlier designer findings are still present |
+| `iamu design proposals [--json]` | List design changes proposed across walkthroughs and reviews |
+| `iamu design accept <slug>` | Accept a proposed design change |
+| `iamu design reject <slug>` | Reject a proposed design change |
 
 ### Findings & Review
 
 | Command | Description |
 |---------|-------------|
-| `iamu findings [--open] [--addressed] [--fix-state <state>] [--flagged] [--json [fields]]` | List findings with triage status, fix state and severity |
-| `iamu triage <finding-ref...> --status <status>` | Triage findings (`open`, `resolved`, `dismissed`) |
+| `iamu findings [--open] [--addressed] [--fix-state <state>] [--json [fields]]` | List findings with triage status, fix state and severity |
+| `iamu triage <finding-ref...> --status <status>` | Triage findings (`open`, `addressed`, `dismissed`) |
 | `iamu report [scenario] [--json]` | View walkthrough reports and finding summaries |
 | `iamu prune [--keep <n>] [--days <n>]` | Prune old runs and reclaim disk space |
 

package/dist/adapters/registry.d.ts

@@ -1,4 +1,10 @@
 import type { HostAdapter } from "./types.js";
+/**
+ * How every host starts the `iamu-sync` MCP server. `npx` rather than a
+ * bare `iamu`: the MCP file is committed, and a teammate without a global
+ * install must still get a working server.
+ */
+export declare const SYNC_SERVER_COMMAND: readonly string[];
 export declare const HOST_ADAPTERS: HostAdapter[];
 /**
  * Detect which host editors are present in the given project root.

package/dist/adapters/types.d.ts

@@ -9,11 +9,28 @@ export interface CommandContent {
 export interface HostAdapter {
     name: string;
     value: string;
+    /** Files or directories (relative to the project root) that mark the host. */
     detectionPaths: string[];
-    supportsSkills: boolean;
+    /** Where the host reads project skills (`<dir>/<name>/SKILL.md`). */
     getSkillsDir(projectRoot: string): string;
-    getCommandPath(projectRoot: string, commandId: string): string;
-    formatCommand(content: CommandContent): string;
-    getMcpConfigPath(projectRoot: string): string;
-    formatMcpConfig(serverCommand: string[]): string;
+    /**
+     * Skill directories an older CLI wrote for this host and the host does
+     * not read. CLI-written skills there are removed on `iamu update`, and
+     * an iamu skill there marks the host as installed.
+     */
+    legacySkillsDirs?(projectRoot: string): string[];
+    /**
+     * Where an older CLI wrote the command file `commandId` for this host.
+     * Nothing is written there any more; it is read only to recognise an
+     * existing install.
+     */
+    legacyCommandPath(projectRoot: string, commandId: string): string;
+    /**
+     * The project-level MCP config file, or `null` when the host reads MCP
+     * servers only from a user-level config (or its own CLI) that iamu does
+     * not write. Then {@link HostAdapter.manualMcpSetup} says what to do.
+     */
+    getMcpConfigPath(projectRoot: string): string | null;
+    /** One line telling the user how to add `iamu-sync` by hand. */
+    manualMcpSetup?: string;
 }