npm - grounder - Versions diffs - 0.2.0 → 0.4.0 - Mend

grounder 0.2.0 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (165) hide show

package/README.md +179 -66
package/dist/agents/claude.d.ts +1 -0
package/dist/agents/claude.d.ts.map +1 -1
package/dist/agents/claude.js +37 -13
package/dist/agents/claude.js.map +1 -1
package/dist/agents/cursor.d.ts +1 -0
package/dist/agents/cursor.d.ts.map +1 -1
package/dist/agents/cursor.js +37 -13
package/dist/agents/cursor.js.map +1 -1
package/dist/agents/hook-runtime.d.ts +65 -21
package/dist/agents/hook-runtime.d.ts.map +1 -1
package/dist/agents/hook-runtime.js +172 -31
package/dist/agents/hook-runtime.js.map +1 -1
package/dist/agents/index.d.ts +18 -0
package/dist/agents/index.d.ts.map +1 -1
package/dist/agents/index.js +27 -4
package/dist/agents/index.js.map +1 -1
package/dist/agents/install-command.d.ts +35 -0
package/dist/agents/install-command.d.ts.map +1 -0
package/dist/agents/install-command.js +65 -0
package/dist/agents/install-command.js.map +1 -0
package/dist/agents/types.d.ts +19 -1
package/dist/agents/types.d.ts.map +1 -1
package/dist/cli.js +62 -60
package/dist/cli.js.map +1 -1
package/dist/commands/apply-agent-installs.d.ts +34 -0
package/dist/commands/apply-agent-installs.d.ts.map +1 -0
package/dist/commands/apply-agent-installs.js +137 -0
package/dist/commands/apply-agent-installs.js.map +1 -0
package/dist/commands/doctor.d.ts.map +1 -1
package/dist/commands/doctor.js +278 -60
package/dist/commands/doctor.js.map +1 -1
package/dist/commands/handoff/list.d.ts +15 -7
package/dist/commands/handoff/list.d.ts.map +1 -1
package/dist/commands/handoff/list.js +21 -13
package/dist/commands/handoff/list.js.map +1 -1
package/dist/commands/handoff/peek.d.ts +5 -2
package/dist/commands/handoff/peek.d.ts.map +1 -1
package/dist/commands/handoff/peek.js +47 -6
package/dist/commands/handoff/peek.js.map +1 -1
package/dist/commands/handoff.d.ts.map +1 -1
package/dist/commands/handoff.js +5 -0
package/dist/commands/handoff.js.map +1 -1
package/dist/commands/migrate.d.ts +23 -0
package/dist/commands/migrate.d.ts.map +1 -0
package/dist/commands/migrate.js +104 -0
package/dist/commands/migrate.js.map +1 -0
package/dist/commands/note/list.d.ts +28 -0
package/dist/commands/note/list.d.ts.map +1 -0
package/dist/commands/note/list.js +72 -0
package/dist/commands/note/list.js.map +1 -0
package/dist/commands/note.d.ts.map +1 -1
package/dist/commands/note.js +6 -1
package/dist/commands/note.js.map +1 -1
package/dist/commands/output.d.ts +27 -0
package/dist/commands/output.d.ts.map +1 -0
package/dist/commands/output.js +51 -0
package/dist/commands/output.js.map +1 -0
package/dist/commands/package-version-notice.d.ts +18 -0
package/dist/commands/package-version-notice.d.ts.map +1 -0
package/dist/commands/package-version-notice.js +39 -0
package/dist/commands/package-version-notice.js.map +1 -0
package/dist/commands/path/logs.d.ts +1 -1
package/dist/commands/path/logs.d.ts.map +1 -1
package/dist/commands/path/logs.js +6 -1
package/dist/commands/path/logs.js.map +1 -1
package/dist/commands/path/notes.d.ts +1 -1
package/dist/commands/path/notes.d.ts.map +1 -1
package/dist/commands/path/notes.js +6 -1
package/dist/commands/path/notes.js.map +1 -1
package/dist/commands/path/plans.d.ts +7 -0
package/dist/commands/path/plans.d.ts.map +1 -0
package/dist/commands/path/plans.js +22 -0
package/dist/commands/path/plans.js.map +1 -0
package/dist/commands/plan/list.d.ts +31 -0
package/dist/commands/plan/list.d.ts.map +1 -0
package/dist/commands/plan/list.js +75 -0
package/dist/commands/plan/list.js.map +1 -0
package/dist/commands/plan.d.ts +34 -0
package/dist/commands/plan.d.ts.map +1 -0
package/dist/commands/plan.js +121 -0
package/dist/commands/plan.js.map +1 -0
package/dist/commands/repo/init.d.ts.map +1 -1
package/dist/commands/repo/init.js +12 -1
package/dist/commands/repo/init.js.map +1 -1
package/dist/commands/status.d.ts +1 -1
package/dist/commands/status.d.ts.map +1 -1
package/dist/commands/status.js +62 -18
package/dist/commands/status.js.map +1 -1
package/dist/commands/upgrade-banner.d.ts +9 -0
package/dist/commands/upgrade-banner.d.ts.map +1 -0
package/dist/commands/upgrade-banner.js +27 -0
package/dist/commands/upgrade-banner.js.map +1 -0
package/dist/commands/vault/init.d.ts.map +1 -1
package/dist/commands/vault/init.js +18 -29
package/dist/commands/vault/init.js.map +1 -1
package/dist/connector/repo.d.ts +2 -0
package/dist/connector/repo.d.ts.map +1 -1
package/dist/connector/repo.js +12 -1
package/dist/connector/repo.js.map +1 -1
package/dist/connector/state.d.ts +86 -0
package/dist/connector/state.d.ts.map +1 -0
package/dist/connector/state.js +171 -0
package/dist/connector/state.js.map +1 -0
package/dist/connector/unsupported-schema.d.ts +9 -0
package/dist/connector/unsupported-schema.d.ts.map +1 -0
package/dist/connector/unsupported-schema.js +14 -0
package/dist/connector/unsupported-schema.js.map +1 -0
package/dist/connector/vault.d.ts +2 -0
package/dist/connector/vault.d.ts.map +1 -1
package/dist/connector/vault.js +6 -1
package/dist/connector/vault.js.map +1 -1
package/dist/help.d.ts +45 -0
package/dist/help.d.ts.map +1 -0
package/dist/help.js +368 -0
package/dist/help.js.map +1 -0
package/dist/util/fs.d.ts +6 -0
package/dist/util/fs.d.ts.map +1 -1
package/dist/util/fs.js +15 -1
package/dist/util/fs.js.map +1 -1
package/dist/util/hash.d.ts +3 -0
package/dist/util/hash.d.ts.map +1 -0
package/dist/util/hash.js +6 -0
package/dist/util/hash.js.map +1 -0
package/dist/util/parse-args.d.ts.map +1 -1
package/dist/util/parse-args.js +11 -2
package/dist/util/parse-args.js.map +1 -1
package/dist/util/path.d.ts +10 -0
package/dist/util/path.d.ts.map +1 -1
package/dist/util/path.js +31 -0
package/dist/util/path.js.map +1 -1
package/dist/util/plan-name.d.ts +10 -0
package/dist/util/plan-name.d.ts.map +1 -0
package/dist/util/plan-name.js +18 -0
package/dist/util/plan-name.js.map +1 -0
package/dist/util/semver.d.ts +10 -0
package/dist/util/semver.d.ts.map +1 -0
package/dist/util/semver.js +40 -0
package/dist/util/semver.js.map +1 -0
package/dist/vault/layout.d.ts +2 -0
package/dist/vault/layout.d.ts.map +1 -1
package/dist/vault/layout.js +4 -0
package/dist/vault/layout.js.map +1 -1
package/dist/vault/list-notes.d.ts +15 -0
package/dist/vault/list-notes.d.ts.map +1 -0
package/dist/vault/list-notes.js +44 -0
package/dist/vault/list-notes.js.map +1 -0
package/dist/vault/list-plans.d.ts +11 -0
package/dist/vault/list-plans.d.ts.map +1 -0
package/dist/vault/list-plans.js +40 -0
package/dist/vault/list-plans.js.map +1 -0
package/dist/vault/write-plan.d.ts +28 -0
package/dist/vault/write-plan.d.ts.map +1 -0
package/dist/vault/write-plan.js +61 -0
package/dist/vault/write-plan.js.map +1 -0
package/package.json +5 -3
package/templates/agents/claude/commands/grounder-note.md +25 -3
package/templates/agents/claude/commands/grounder-plan.md +69 -0
package/templates/agents/claude/commands/grounder-task-handoff.md +3 -3
package/templates/agents/claude/commands/grounder-task.md +5 -3
package/templates/agents/cursor/commands/grounder-note.md +26 -4
package/templates/agents/cursor/commands/grounder-plan.md +69 -0
package/templates/agents/cursor/commands/grounder-task-handoff.md +4 -4
package/templates/agents/cursor/commands/grounder-task.md +6 -4
package/templates/vault/plan.md +16 -0

package/templates/agents/cursor/commands/grounder-note.md CHANGED Viewed

@@ -1,11 +1,33 @@
 Save a note to the Obsidian vault for this project.
-Run from the linked project folder or any subdirectory beneath it:
+Distill the instruction after `/grounder-note` into a clean note body — not a chat transcript.
+Do not dump tool traces, full conversation, or false starts.
-  npx grounder note "<user text>"
+**Special case: the instruction asks to view existing notes, not write one** (`list`, `list 3 oldest`, `show notes`, etc.) → run `{{GROUNDER_CLI}} note list --limit <N>` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no note write. Relay the CLI stdout as-is (it already includes the count header).
-The vault is outside the workspace — approve shell permissions if Cursor prompts you.
+Rules:
+- Default → distill the args into a clean note body
+- Exact wording marked to keep (quoted, "save exactly:"/"verbatim:", or a fenced block) → use that verbatim instead, unmodified
+- Empty args → distill the central point of the current thread instead
+Then run from the linked project folder or any subdirectory beneath it:
+  {{GROUNDER_CLI}} note "<body>"
+Optional short title slug (filename):
+  {{GROUNDER_CLI}} note --title <slug> "<body>"
+For multi-line bodies, prefer a shell heredoc so quoting does not break:
+```bash
+{{GROUNDER_CLI}} note "$(cat <<'EOF'
+…
+EOF
+)"
+```
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
-Use the text after `/grounder-note` as the note body.
 Do not compute vault paths or write files yourself — the CLI handles it.
 Report the CLI output path from stdout to the user.

package/templates/agents/cursor/commands/grounder-plan.md ADDED Viewed

@@ -0,0 +1,69 @@
+Write a named, updatable plan document to the Obsidian vault for this project.
+Distill the instruction after `/grounder-plan` into a structured plan — not a chat transcript.
+Do not dump tool traces, full conversation, or false starts.
+Build a markdown body with these sections:
+```markdown
+# Plan: <title>
+## Goal
+…
+## Steps
+1. …
+2. …
+## Decisions / open questions
+- …
+## Status
+…
+```
+**Special case: the instruction asks to view existing plans, not name a new topic** (`list`, `list 3 oldest`, `show plans`, etc.) → run `{{GROUNDER_CLI}} plan list --limit <N>` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no plan write, no title. Relay the CLI stdout as-is (it already includes the count header).
+Otherwise, resolve the target, then **state it plainly before writing** — `Updating plan at <path>.` or `Creating new plan titled <title>.` This is a visible record, not a blocking confirmation — updates overwrite with no `--force`, so get the match right.
+**1. Known path** (attached/open in chat, or printed by an earlier `grounder plan` this conversation) → update it directly.
+**2. No path, but update intent** (e.g. "update/continue/revise the plan", or a name that sounds like an existing one) → look it up first:
+```bash
+{{GROUNDER_CLI}} plan list --limit 5
+```
+CLI output starts with a count header, then each result as a numbered two-line block — `N. ` + title (filename stem) on the first line, the absolute path indented beneath it.
+A match counts only if its title actually corresponds to what the user named — not just "it's the only plan in the project." No name given and exactly one plan exists → that counts too. If the user refers to a plan by the number shown in *this* listing (e.g. "update plan 2"), that counts as a match too — resolve it to the path from this same output, don't reuse a number from an earlier listing in the conversation (it's positional, not a stable id, and can shift if plans changed since). Otherwise (no match, several matches, or a name/number that doesn't correspond to any existing plan) → ask; never guess.
+Cases 1 and 2 (update) — run:
+```bash
+{{GROUNDER_CLI}} plan "$(cat <<'EOF'
+# Plan: …
+…
+EOF
+)" --path <path>
+```
+`--path` must resolve under this project's `plans/` dir; it always overwrites (no `--force`).
+**3. No path, no update intent → genuinely new plan.** Derive a `--title` (the user's explicit name, else a short kebab-case slug from the plan's title/goal) and write immediately — don't ask about the name itself.
+```bash
+{{GROUNDER_CLI}} plan "$(cat <<'EOF'
+# Plan: …
+…
+EOF
+)" --title <name>
+```
+If `--title` collides with an existing plan (non-zero exit; stderr names the conflict), ask: overwrite (`--force`) or a different name. `--force` only resolves that collision — **never** use it to update a plan you meant to target with `--path`.
+Run from the linked project folder or any subdirectory beneath it.
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
+Do not compute vault paths or write files yourself — the CLI handles it.
+Report the exact path the CLI prints on stdout — it confirms the real outcome, not just the intent.

package/templates/agents/cursor/commands/grounder-task-handoff.md CHANGED Viewed

@@ -32,23 +32,23 @@ Rules:
 Then run from the linked project folder or any subdirectory beneath it:
-  npx grounder handoff "<body>"
+  {{GROUNDER_CLI}} handoff "<body>"
 Optional short title slug (filename + frontmatter):
-  npx grounder handoff --title <slug> "<body>"
+  {{GROUNDER_CLI}} handoff --title <slug> "<body>"
 For multi-line bodies, prefer a shell heredoc so quoting does not break:
 ```bash
-npx grounder handoff "$(cat <<'EOF'
+{{GROUNDER_CLI}} handoff "$(cat <<'EOF'
 # Handoff: …
 …
 EOF
 )"
 ```
-The vault is outside the workspace — approve shell permissions if Cursor prompts you.
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
 Do not compute vault paths or write files yourself — the CLI handles it.
 Report the CLI output path from stdout to the user.

package/templates/agents/cursor/commands/grounder-task.md CHANGED Viewed

@@ -2,19 +2,21 @@ Hydrate this session from the latest vault handoff and repo truth.
 Read-only — do not write to the vault. Do not invent vault paths.
-From the linked project folder or any subdirectory beneath it:
+**Special case: the instruction asks to view existing handoffs, not hydrate** (`list`, `list 3 oldest`, `show handoffs`, etc.) → run `{{GROUNDER_CLI}} handoff list --limit <N>` (N = count named, else 5; ignore order words like "oldest" — output is always newest-first, never resort or relabel it) and stop — no hydrate, no `AGENTS.md`, no “start work.” Relay the CLI stdout as-is (it already includes the count header).
+Otherwise, from the linked project folder or any subdirectory beneath it:
 1. Get the current handoff (skips empty/unreadable files, same pick as the session-start teaser):
-   npx grounder handoff list --head
+   {{GROUNDER_CLI}} handoff list --head
 2. If empty: tell the user there are no handoffs yet, then read repo `AGENTS.md` only and proceed.
-3. Otherwise, read that file. If the user names a specific session instead, run `npx grounder handoff list --limit 5` and read the path they mean.
+3. Otherwise, read that file. If the user names a specific session instead: `{{GROUNDER_CLI}} handoff list --limit 5` → match name/index to the indented path in *this* listing (positional, not a stable id). Miss → once with `--limit 50` (*that* listing only). Still miss → tell the user and stop — no guessed hydrate.
 4. Read repo `AGENTS.md` (project conventions and constraints).
 5. Summarize briefly what is next (from the handoff `## Next` section when present), then start work.
-The vault is outside the workspace — approve shell permissions if Cursor prompts you.
+Run {{GROUNDER_CLI}} with `required_permissions: ["all"]` (vault is outside the workspace).
 Use free-text after `/grounder-task` as optional focus (session name, index, or task hint).

package/templates/vault/plan.md ADDED Viewed

@@ -0,0 +1,16 @@
+<!-- Reference shape for /grounder-plan. Not installed or filled by the CLI — slash commands embed this structure. -->
+# Plan: <title>
+## Goal
+…
+## Steps
+1. …
+2. …
+## Decisions / open questions
+- …
+## Status
+…