claudify-agent 1.0.12 → 1.0.14

package/.claude/commands/backbone-init.md

@@ -17,7 +17,9 @@ Draft or refresh `BACKBONE.md` at the project root. Notes from me: $ARGUMENTS
    - Invariants: only rules found in docs or that I confirm. Never invent business rules.
 3. Keep it under ~80 lines. Link, never copy.
 4. List what you could not determine as questions, batched in one message.
-5. Set `Last synced: <HEAD short sha> (<date>)` so `/backbone-sync` can diff from here.
+5. Set the `Last synced:` line so `/backbone-sync` can diff from here:
+   - single repo: `Last synced: <date> | <HEAD short sha>`;
+   - multi-repo workspace (root is not a git repo): `Last synced: <date> | <repo-dir>@<sha> <repo-dir>@<sha> ...`, one entry per sub-repo.
 6. Slim `CLAUDE.md`: it is loaded every session too, so project facts in it are paid twice. Only touch content OUTSIDE the `<!-- claudify:start -->`…`<!-- claudify:end -->` block. If that content is more than ~30 lines, propose:
    - project facts (overview, repos, structure, commands) → the matching `BACKBONE.md` section;
    - must-follow rules and known traps → `BACKBONE.md` Invariants;

package/.claude/commands/backbone-sync.md

@@ -6,7 +6,7 @@ argument-hint: [area to focus on]
 Sync `BACKBONE.md` with the code as it is now. Focus: $ARGUMENTS
 
 1. Find what changed since the last sync:
-   - read the `Last synced:` commit in `BACKBONE.md`; run `git log --stat <commit>..HEAD` (and `git status` for uncommitted work);
+   - read the `Last synced:` line in `BACKBONE.md`. Single repo `<date> | <sha>`: run `git log --stat <sha>..HEAD` and `git status`. Multi-repo `<date> | <repo>@<sha> ...`: run the same inside each `<repo>` (`git -C <repo> log --stat <sha>..HEAD`); a sub-repo not listed is new, a listed one that is gone was removed;
    - no commit recorded → fall back to the shallow scan of `/backbone-init`.
    Read only the changed files that matter (manifests, new dirs, new docs, CI, public APIs); not every diff line.
 2. Compare against `BACKBONE.md` section by section and list gaps:
@@ -18,4 +18,4 @@ Sync `BACKBONE.md` with the code as it is now. Focus: $ARGUMENTS
 3. Also compare with `spec/specs/*.md` for the touched areas. Report code that contradicts an archived requirement, but do not edit specs: that is my call (fix the code or open a change).
 4. Ask me about anything you cannot decide from evidence, batched in one message. Never invent invariants.
 5. If `CLAUDE.md` outside the claudify block grew past ~30 lines or repeats backbone facts, propose slimming it exactly as in step 6 of `.claude/commands/backbone-init.md`.
-6. Show the diff (`BACKBONE.md` including `Last synced: <HEAD short sha> (<date>)`, plus `CLAUDE.md` if slimming) and wait for my approval before writing.
+6. Show the diff (`BACKBONE.md` including the refreshed `Last synced:` line in the same format, every sub-repo at its current HEAD, plus `CLAUDE.md` if slimming) and wait for my approval before writing.

package/.claude/package.json

@@ -0,0 +1,4 @@
+{
+  "private": true,
+  "type": "module"
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claudify-agent",
-  "version": "1.0.12",
+  "version": "1.0.14",
   "description": "Enterprise-grade workflow & context optimization framework for Claude Code, Claude Desktop, and AI coding agents.",
   "repository": {
     "type": "git",

package/templates/BACKBONE.md

@@ -3,7 +3,7 @@
 > Loaded every session. A map, not documentation: link to details, never copy them. Keep under ~80 lines.
 > Fill with `/backbone-init`; kept in sync by `/spec-new`, `/spec-archive` and `/learn`; after work done without specs, run `/backbone-sync`.
 
-Last synced: <commit> (<date>)
+Last synced: <date> | <sha>   (multi-repo: <date> | <repo>@<sha> <repo>@<sha> ...)
 
 ## Overview
 - What: <one or two lines: what the system does and for whom>