first-tree 0.0.6 → 0.0.8

package/skills/first-tree/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: first-tree
-description: Maintain the canonical `first-tree` skill and the thin `context-tree` CLI distributed by the `first-tree` npm package. Use when modifying `context-tree` commands (`init`, `verify`, `upgrade`, `help onboarding`), the installed skill payload under `assets/framework/`, maintainer references, or the build, packaging, test, and CI wiring that supports the framework.
+description: Maintain the canonical `first-tree` skill and the thin `context-tree` CLI distributed by the `first-tree` npm package. Use when modifying `context-tree` commands (`init`, `publish`, `verify`, `upgrade`, `help onboarding`), the installed skill payload under `assets/framework/`, maintainer references, or the build, packaging, test, and CI wiring that supports the framework.
 ---
 
 # First Tree
@@ -59,6 +59,10 @@ repos.
 
 ### Working In A User Tree Repo
 
+- When the task is to "install and use first-tree" in an existing
+  source/workspace repo, start with
+  `references/source-workspace-installation.md` and follow that workflow
+  end-to-end before improvising.
 - When a user asks to install first-tree for an existing source/workspace repo,
   the current repo keeps only the installed skill plus a
   `FIRST-TREE-SOURCE-INTEGRATION:` line in `AGENTS.md` and `CLAUDE.md`. Do not
@@ -68,20 +72,35 @@ repos.
   into the source/workspace repo and scaffolds tree files only in the
   dedicated tree repo. Use `--here` to initialize the current repo in place
   when you are already inside the tree repo.
+- `context-tree publish --open-pr` is the default second-stage command after
+  `init` for source/workspace installs. Run it from the dedicated tree repo
+  once the initial tree version is ready to push.
+- Never run `context-tree init --here` in a source/workspace repo unless the
+  user explicitly wants that repo itself to become the dedicated Context Tree.
+  `--here` is for when you have already switched into the `*-context` repo.
 - `context-tree init` installs this skill into the target tree repo and
   scaffolds `.agents/skills/first-tree/`, `.claude/skills/first-tree/`,
   `NODE.md`, `AGENTS.md`, and `members/NODE.md`.
-- The default source/workspace workflow is: create or reuse `<repo>-context`,
-  prefer pushing it in the same GitHub organization as the source repo, add it
-  back to the source/workspace repo as a git submodule, and open a PR to the
-  source/workspace repo's default branch instead of merging automatically.
+- The default source/workspace workflow is: run `context-tree init` from the
+  source repo, draft the first tree version in `<repo>-context`, then run
+  `context-tree publish --open-pr` from that dedicated tree repo.
+- After `context-tree publish` succeeds, treat the source/workspace repo's
+  submodule checkout as the canonical local working copy for the tree. The
+  temporary sibling bootstrap checkout can be deleted when you no longer need
+  it.
+- If the dedicated tree repo was initialized manually with `context-tree init --here`
+  and does not have bootstrap metadata yet, pass `--source-repo PATH` to
+  `context-tree publish`.
+- If permissions, auth, or local filesystem constraints block the dedicated
+  repo workflow, stop and report the blocker. Do not fall back to in-place tree
+  bootstrap in the source/workspace repo.
 - `context-tree upgrade` refreshes the installed skill from the copy bundled
   with the currently running `first-tree` package. In a source/workspace repo
   it refreshes only the local skill plus the
   `FIRST-TREE-SOURCE-INTEGRATION:` line; upgrade the dedicated tree repo
   separately with `--tree-path`. To pick up a newer framework, run a newer
   package version first. It also migrates older repos that still use
-  `skills/first-tree/` or `skills/first-tree-cli-framework/`.
+  `skills/first-tree/`.
 - The user's tree content lives outside the skill; the skill only carries the
   reusable framework payload plus maintenance guidance.
 - The tree still stores decisions, constraints, and ownership; execution detail

package/skills/first-tree/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "First Tree"
   short_description: "Maintain the First Tree skill and thin Context Tree CLI"
-  default_prompt: "Use $first-tree to maintain the canonical first-tree skill, its thin context-tree CLI, or its build, packaging, test, eval, and CI wiring. When a source/workspace repo installs first-tree, keep that repo limited to local skill integration plus the FIRST-TREE-SOURCE-INTEGRATION marker lines, and keep all NODE.md/tree content only in a dedicated sibling *-context repo."
+  default_prompt: "Use $first-tree to maintain the canonical first-tree skill, its thin context-tree CLI, or its build, packaging, test, eval, and CI wiring. When a source/workspace repo installs first-tree, read references/source-workspace-installation.md first, keep that repo limited to local skill integration plus the FIRST-TREE-SOURCE-INTEGRATION marker lines, and keep all NODE.md/tree content only in a dedicated sibling *-context repo. Never choose context-tree init --here in the source/workspace repo unless the user explicitly wants that repo itself to become the tree."

package/skills/first-tree/assets/framework/VERSION

@@ -1 +1 @@
-0.2.0
+0.2.2

package/skills/first-tree/engine/commands/publish.ts

@@ -0,0 +1,5 @@
+export {
+  PUBLISH_USAGE,
+  parsePublishArgs,
+  runPublishCli as runPublish,
+} from "#skill/engine/publish.js";

package/skills/first-tree/engine/init.ts

@@ -16,6 +16,7 @@ import {
   renderTemplateFile,
   resolveBundledPackageRoot,
 } from "#skill/engine/runtime/installer.js";
+import { writeBootstrapState } from "#skill/engine/runtime/bootstrap.js";
 import {
   AGENT_INSTRUCTIONS_FILE,
   AGENT_INSTRUCTIONS_TEMPLATE,
@@ -42,8 +43,11 @@ the first-tree skill in the current repo, updates \`AGENTS.md\` and \`CLAUDE.md\
 with a \`${SOURCE_INTEGRATION_MARKER}\` line, and creates a sibling dedicated tree
 repo named \`<repo>-context\`.
 
+Do not use \`--here\` inside a source/workspace repo unless you explicitly want
+that repo itself to become the Context Tree.
+
 Options:
-  --here             Initialize the current repo in place
+  --here             Initialize the current repo in place after you are already in the dedicated tree repo
   --tree-name NAME   Name the dedicated sibling tree repo to create
   --tree-path PATH   Use an explicit tree repo path
   --help             Show this help message
@@ -119,13 +123,10 @@ export function formatTaskList(
       );
       lines.push("## Source Workspace Workflow");
       lines.push(
-        `- [ ] Publish this dedicated tree repo to the same GitHub organization as \`${context.sourceRepoName}\``,
-      );
-      lines.push(
-        `- [ ] Add this tree repo back to \`${context.sourceRepoName}\` as a git submodule after the remote exists`,
+        `- [ ] When this initial tree version is ready, run \`context-tree publish --open-pr\` from this dedicated tree repo. It will create or reuse the GitHub \`*-context\` repo, add it back to \`${context.sourceRepoName}\` as a git submodule, and open the source/workspace PR.`,
       );
       lines.push(
-        `- [ ] Open a PR against the source/workspace repo's default branch with only the installed skill, the \`${SOURCE_INTEGRATION_MARKER}\` marker lines in \`${AGENT_INSTRUCTIONS_FILE}\` / \`${CLAUDE_INSTRUCTIONS_FILE}\`, and the new submodule pointer`,
+        `- [ ] After publish succeeds, treat the source/workspace repo's \`${context.sourceRepoName}\` submodule checkout as the canonical local working copy for this tree. The temporary sibling bootstrap repo can be deleted when you no longer need it.`,
       );
       lines.push("");
     }
@@ -202,6 +203,15 @@ export function runInit(repo?: Repo, options?: InitOptions): number {
     return 1;
   }
   const r = initTarget.repo;
+  if (options?.here && sourceRepo.isLikelySourceRepo() && !sourceRepo.looksLikeTreeRepo()) {
+    console.log(
+      "Warning: `context-tree init --here` is initializing this source/workspace" +
+        " repo in place. This will create `NODE.md`, `members/`, and tree-scoped" +
+        ` ${AGENT_INSTRUCTIONS_FILE} here. Use plain \`context-tree init\` to create` +
+        " a sibling dedicated tree repo instead.",
+    );
+    console.log();
+  }
   const taskListContext = initTarget.dedicatedTreeRepo
     ? {
         dedicatedTreeRepo: true,
@@ -287,6 +297,14 @@ export function runInit(repo?: Repo, options?: InitOptions): number {
     }
   }
 
+  if (initTarget.dedicatedTreeRepo) {
+    writeBootstrapState(r.root, {
+      sourceRepoName: sourceRepo.repoName(),
+      sourceRepoPath: relativePathFrom(r.root, sourceRepo.root),
+      treeRepoName: r.repoName(),
+    });
+  }
+
   console.log(ONBOARDING_TEXT);
   console.log("---\n");