The tickets, queue and logs skills are tracked files of gemstack

[suleimansh]

The cutover step from #1777. The daemon links only branches and work-queue into a checkout now. The tickets, queue and logs skills are the project's own tracked files.

Three copies of the packages' SKILL.md at 06ea480 under .agents/skills/<name>/, with the .claude/skills/<name> links, the way the logic-driven-development skill is tracked. The four @gemstack/skill-* packages were already in the root devDependencies, so npx tickets resolves.

The copies drift from the packages' files as those change. Keeping them in step is by hand for now.

🤖 automated · Fable 5.1, effort high

[suleimansh]

👤 The prompts that drove this PR, verbatim. Under each, one 🤖 line on what the agent did with it.

1.

Context: gemstack. Read memory first: tf-rom-review-2026-09-14.md (Rom's two review rounds, my answers, the merge, the package name), tf-daemon-half-plan-next.md (what #1777 is and how it was built), rom-slop-rules.md, ask-before-starting-work.md, tf-no-compat-no-bloat.md, no-claude-attribution.md, tf-effort-marker.md, tf-logic-md-rename.md, the-framework-dogfood-loop.md.

State: PR #1777 is merged, merge commit 06ea480 on main. My main checkout and the :4200 daemon still run the old build. Agreed with Rom: the next PR splits packages/routines into one package per command, named @gemstack/skill-, so @gemstack/skill-work-queue first.

Rules: design and naming picks are mine or Rom's, never yours; give me facts, I decide. Every post is marked 🤖 with the effort I state. Every PR gets a 👤 comment with my prompts verbatim, unedited. Ask me before any push, merge, post, or daemon restart.

Open, in this order:

1. The cutover, step by step, each step on my word: pull main into my checkout and pnpm build; in gemstack and the other registered projects, track the tickets, queue and logs SKILL.md files under .agents/skills// with the .claude/skills/ links, and check the four @gemstack/skill-* packages are listed; restart the :4200 daemon (the recipe is in the-framework-dogfood-loop.md). Then read the daemon log and tell me what the first look said.
2. The next PR, in a scratchpad worktree off main: replace packages/routines with packages/skill-work-queue, package @gemstack/skill-work-queue, SKILL.md only, the framework depending on it for now. Rewrite "What remains" in the PR body and in the Dashboard architecture: the plan and six questions #1774 comment (Q6.5) around Rom's skill-schedule idea, a scheduler skill the user configures with agent-schedule.md in main that runs any command skill, instead of front-matter triggers and a scheduler package. Update LOGIC.md and DECISIONS.md. opening.
3. If Rom asks for it: move "before you stop, release anything you still hold" from the
   work-queue command to the branchess.
4. Dogfood on gemstack for a few days: queue a real entry, watch the chain, read the daemon
   log. Report what you see.
5. Then the next design question, "do we still need the daemon?", as a comment on Dashboard architecture: the plan and six questions #1774 in the
   Q-shape with a story: the dashboar, agent-driver writing the live
   log, skill-schedule running comman live process. Show me the draft
   before posting.

If I paste new Discord lines from ell me what he asks, one pointeach, plainly. I answer him myself

🤖 Read the memory files, then gathered the facts for step 1 without touching anything: local main one commit behind, daemon pid 87576 on the old build, three registered projects, which of them track skill files and list the packages (only gemstack lists the packages, none tracks the files), the packages are not on npm. Reported and waited.

2.

go ahead

🤖 Pulled main to 06ea480, pnpm build. Noted the old daemon serves the dist directory from disk, so the bundle comparison proved nothing, and a stale dist/todo-loop.js is left over. Asked two questions: branch or main, and what to do with the two throwaway projects.

3.

1. branch and PR
2. what you mean?

🤖 Explained question 2: the two throwaway projects have neither the files nor the bins, and the packages are not on npm, so wiring them means file: paths to the gemstack checkout. Created the branch, copied the three SKILL.md files, added the links. Found the old daemon had excluded the tickets and queue paths in the local .git/info/exclude, removed the four stale lines, committed 1c4ba86. Drafted the PR body and asked for the effort level.

4.

1. open the PR
2. the effort is high
3. skip them
   --
   tell me what next steps

🤖 Pushed the branch, opened this PR, posted this comment.