first-tree 0.0.3 → 0.0.4

package/skills/first-tree/tests/verify.test.ts

@@ -1,19 +1,23 @@
-import { mkdirSync, writeFileSync } from "node:fs";
+import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
 import { join } from "node:path";
 import { describe, expect, it } from "vitest";
+import { runInit } from "#skill/engine/init.js";
 import { check, checkProgress, runVerify } from "#skill/engine/verify.js";
 import { Repo } from "#skill/engine/repo.js";
 import {
+  AGENT_INSTRUCTIONS_FILE,
   INSTALLED_PROGRESS,
   LEGACY_PROGRESS,
 } from "#skill/engine/runtime/asset-loader.js";
 import {
   useTmpDir,
+  makeAgentsMd,
   makeFramework,
   makeLegacyFramework,
   makeNode,
-  makeAgentMd,
+  makeSourceRepo,
   makeMembers,
+  makeSourceSkill,
 } from "./helpers.js";
 
 // --- check ---
@@ -88,10 +92,7 @@ function buildFullRepo(root: string): void {
     join(root, "NODE.md"),
     "---\ntitle: My Org\nowners: [alice]\n---\n# Content\n",
   );
-  writeFileSync(
-    join(root, "AGENT.md"),
-    "<!-- BEGIN CONTEXT-TREE FRAMEWORK -->\nstuff\n<!-- END CONTEXT-TREE FRAMEWORK -->\n",
-  );
+  makeAgentsMd(root, { markers: true });
   makeMembers(root, 1);
 }
 
@@ -108,6 +109,74 @@ describe("runVerify all passing", () => {
     const ret = runVerify(repo, passValidator);
     expect(ret).toBe(0);
   });
+
+  it("passes after a real init flow when only the user tree remains to validate", () => {
+    const repoDir = useTmpDir();
+    const sourceDir = useTmpDir();
+    mkdirSync(join(repoDir.path, ".git"));
+    makeSourceSkill(sourceDir.path, "0.2.0");
+
+    expect(runInit(new Repo(repoDir.path), { sourceRoot: sourceDir.path })).toBe(0);
+
+    writeFileSync(
+      join(repoDir.path, "NODE.md"),
+      [
+        "---",
+        'title: "Example Tree"',
+        "owners: [alice]",
+        "---",
+        "",
+        "# Example Tree",
+        "",
+        "A repository initialized from the bundled skill for verification coverage.",
+        "",
+        "## Domains",
+        "",
+        "- **[members/](members/NODE.md)** — Team member definitions and responsibilities.",
+        "",
+      ].join("\n"),
+    );
+
+    const agentPath = join(repoDir.path, AGENT_INSTRUCTIONS_FILE);
+    writeFileSync(
+      agentPath,
+      `${readFileSync(agentPath, "utf-8").trim()}\n\nProject-specific verification instructions.\n`,
+    );
+
+    mkdirSync(join(repoDir.path, "members", "alice"), { recursive: true });
+    writeFileSync(
+      join(repoDir.path, "members", "alice", "NODE.md"),
+      [
+        "---",
+        'title: "Alice"',
+        "owners: [alice]",
+        'type: "human"',
+        'role: "Maintainer"',
+        "domains:",
+        '  - "members"',
+        "---",
+        "",
+        "# Alice",
+        "",
+        "## About",
+        "",
+        "Maintains the initialized tree and keeps the docs current.",
+        "",
+        "## Current Focus",
+        "",
+        "Validating the init-to-verify workflow.",
+        "",
+      ].join("\n"),
+    );
+
+    const progressPath = join(repoDir.path, INSTALLED_PROGRESS);
+    writeFileSync(
+      progressPath,
+      readFileSync(progressPath, "utf-8").replace(/^- \[ \]/gm, "- [x]"),
+    );
+
+    expect(runVerify(new Repo(repoDir.path))).toBe(0);
+  });
 });
 
 // --- runVerify — failing checks ---
@@ -120,7 +189,7 @@ describe("runVerify failing", () => {
     expect(ret).toBe(1);
   });
 
-  it("fails when AGENT.md is missing", () => {
+  it("fails when AGENTS.md is missing", () => {
     const tmp = useTmpDir();
     makeFramework(tmp.path);
     writeFileSync(
@@ -132,6 +201,28 @@ describe("runVerify failing", () => {
     expect(ret).toBe(1);
   });
 
+  it("fails when only legacy AGENT.md exists", () => {
+    const tmp = useTmpDir();
+    mkdirSync(join(tmp.path, ".git"));
+    makeFramework(tmp.path);
+    makeNode(tmp.path);
+    makeAgentsMd(tmp.path, { legacyName: true, markers: true, userContent: true });
+    makeMembers(tmp.path, 1);
+    const repo = new Repo(tmp.path);
+    const ret = runVerify(repo, passValidator);
+    expect(existsSync(join(tmp.path, AGENT_INSTRUCTIONS_FILE))).toBe(false);
+    expect(ret).toBe(1);
+  });
+
+  it("fails when legacy AGENT.md remains alongside AGENTS.md", () => {
+    const tmp = useTmpDir();
+    buildFullRepo(tmp.path);
+    makeAgentsMd(tmp.path, { legacyName: true, markers: true, userContent: true });
+    const repo = new Repo(tmp.path);
+    const ret = runVerify(repo, passValidator);
+    expect(ret).toBe(1);
+  });
+
   it("fails when node validation returns non-zero", () => {
     const tmp = useTmpDir();
     buildFullRepo(tmp.path);
@@ -139,4 +230,12 @@ describe("runVerify failing", () => {
     const ret = runVerify(repo, failValidator);
     expect(ret).toBe(1);
   });
+
+  it("gives a dedicated-tree hint when run from a source repo", () => {
+    const tmp = useTmpDir();
+    makeSourceRepo(tmp.path);
+    const repo = new Repo(tmp.path);
+    const ret = runVerify(repo, passValidator);
+    expect(ret).toBe(1);
+  });
 });

package/dist/onboarding-6Fr5Gkrk.js

@@ -1,2 +0,0 @@
-import { t as runOnboarding } from "./onboarding-B9zPGvvG.js";
-export { runOnboarding };

package/dist/onboarding-B9zPGvvG.js

@@ -1,10 +0,0 @@
-//#region skills/first-tree/references/onboarding.md
-var onboarding_default = "# Context Tree Onboarding\n\nYou are setting up a **Context Tree** — the living source of truth for an organization. This document tells you what it is and how to bootstrap one.\n\n---\n\n## What Is a Context Tree\n\nA Context Tree is a Git repository where every directory is a **domain** and every file is a **node**. Each node captures decisions, designs, and cross-domain relationships — the knowledge that would otherwise scatter across PRs, documents, and people's heads.\n\nKey properties:\n\n- **Nodes are markdown files.** Each directory has a `NODE.md` that describes the domain. Leaf `.md` files capture specific decisions or designs.\n- **Every node has an owner.** Declared in YAML frontmatter. Owners approve changes to their nodes.\n- **Organized by concern, not by repo or team.** An agent working on \"add SSO\" finds all auth context in one place — not split across 4 repos.\n- **The tree is never a snapshot — it's the current state.** When decisions change, the tree updates. Stale nodes are bugs.\n\n### Frontmatter Format\n\nEvery node has frontmatter:\n\n```yaml\n---\ntitle: \"Auth Architecture\"\nowners: [alice, bob]\nsoft_links: [/infrastructure/deployments]\n---\n```\n\n- `owners` — who can approve changes. `owners: []` inherits from parent. `owners: [*]` means anyone.\n- `soft_links` — cross-references to related nodes in other domains.\n\n### What Belongs in the Tree\n\nInformation an agent needs to **decide** on an approach — not to execute it.\n\n**Yes:** \"Auth spans 4 repos: backend issues JWTs, frontend uses Better Auth, extension uses OAuth popup, desktop uses localhost callback.\"\n\n**No:** The function signature of `auth_service.verify()` — that's in the code.\n\n---\n\n## Four Principles\n\n1. **Source of truth for decisions, not execution.** The tree captures the *what* and *why*. Execution details stay in source systems.\n2. **Agents are first-class participants.** The tree is designed for agents to navigate and update.\n3. **Transparency by default.** Reading is open to all. Writing requires owner approval.\n4. **Git-native.** Nodes are files, domains are directories. History, ownership, and review follow Git conventions.\n\n---\n\n## How to Set Up a Context Tree\n\n### Prerequisites\n\n- A Git repository for your tree (separate from your code repos)\n- Node.js 18+\n- The npm package is `first-tree`, the installed CLI command is\n  `context-tree`, and the installed skill directory in the tree is\n  `skills/first-tree/`\n- Use `npx first-tree init` for one-off runs, or `npm install -g first-tree`\n  to add the `context-tree` command to your PATH\n\n### Step 1: Initialize\n\n```bash\nmkdir my-org-tree && cd my-org-tree\ngit init\ncontext-tree init\n```\n\nThis installs the framework skill into `skills/first-tree/`, renders scaffolding (`NODE.md`, `AGENT.md`, `members/NODE.md`), and generates a task list in `skills/first-tree/progress.md`.\n\n### Step 2: Work Through the Task List\n\nRead `skills/first-tree/progress.md`. It contains a checklist tailored to the current state of the repo. Complete each task:\n\n- Fill in `NODE.md` with your organization name, owners, and domains\n- Add project-specific instructions to `AGENT.md` below the framework markers\n- Create member nodes under `members/`\n- Optionally configure agent integration (e.g., Claude Code session hooks)\n- Copy validation workflows from `skills/first-tree/assets/framework/workflows/` to `.github/workflows/`\n\nAs you complete each task, check it off in `skills/first-tree/progress.md` by changing `- [ ]` to `- [x]`.\n\n### Step 3: Verify\n\n```bash\ncontext-tree verify\n```\n\nThis fails if any items in `skills/first-tree/progress.md` remain unchecked, and runs deterministic checks (valid frontmatter, node structure, member nodes exist).\n\n### Step 4: Design Your Domains\n\nCreate top-level directories for your organization's primary concerns. Each needs a `NODE.md`:\n\n```\nmy-org-tree/\n  NODE.md              # root — lists all domains\n  engineering/\n    NODE.md            # decisions about architecture, infra, tooling\n  product/\n    NODE.md            # strategy, roadmap, user research\n  marketing/\n    NODE.md            # positioning, campaigns\n  members/\n    NODE.md            # team members and agents\n    alice/\n      NODE.md          # individual member node\n```\n\n### Step 5: Populate from Existing Work\n\nFor each domain, extract knowledge from existing repos, docs, and systems:\n\n- Decisions and their rationale\n- Cross-domain relationships and dependencies\n- Constraints that aren't obvious from the code\n\nThe tree doesn't duplicate source code — it captures what connects things and why they were built that way.\n\n---\n\n## CLI Reference\n\n| Command | Description |\n|---------|-------------|\n| `context-tree init` | Bootstrap a new tree. Installs the framework skill, renders templates, generates a task list. |\n| `context-tree verify` | Check the installed progress file for unchecked items + run deterministic validation. |\n| `context-tree upgrade` | Refresh the installed framework skill from the currently running `first-tree` npm package and generate follow-up tasks. |\n| `context-tree help onboarding` | Print this onboarding guide. |\n\n---\n\n## Upgrading the Framework\n\nWhen the framework updates:\n\n```bash\ncontext-tree upgrade\n```\n\n`context-tree upgrade` refreshes `skills/first-tree/` from the\nskill bundled with the currently running `first-tree` npm package, preserves your\ntree content, and generates follow-up tasks in\n`skills/first-tree/progress.md`.\n\nIf your repo still uses the older `skills/first-tree-cli-framework/` path,\n`context-tree upgrade` will migrate it to `skills/first-tree/` first.\n\nTo pick up a newer framework release, first run a newer package version, for\nexample `npx first-tree@latest upgrade`, or update your global `first-tree`\ninstall before running `context-tree upgrade`.\n\n---\n\n## Further Reading\n\n- `skills/first-tree/references/principles.md` — Core principles with detailed examples\n- `skills/first-tree/references/ownership-and-naming.md` — How nodes are named and owned\n- `AGENT.md` in your tree — The before/during/after workflow for every task\n";
-//#endregion
-//#region skills/first-tree/engine/onboarding.ts
-function runOnboarding(output = console.log) {
-	output(onboarding_default);
-	return 0;
-}
-//#endregion
-export { onboarding_default as n, runOnboarding as t };