@erclx/canon 4.86.0 → 4.88.0

package/src/records/size.ts

@@ -87,7 +87,7 @@ interface Walked {
  * already, since these folders are gitignored and hold whatever that disk holds,
  * so a local date is the answer consistent with the rest of the report.
  */
-function day(ms: number): string {
+export function day(ms: number): string {
   const at = new Date(ms)
   const month = String(at.getMonth() + 1).padStart(2, '0')
   const date = String(at.getDate()).padStart(2, '0')
@@ -245,6 +245,29 @@ export async function sizeRecords(
   }
 }
 
+/**
+ * The file count, byte total, and newest `mtime` under one path, for a caller
+ * that wants a unit's freshness rather than the full per-window reading.
+ *
+ * It walks with the same `walk`/`absorb` pair `sizeRecords` uses, so the two
+ * verbs agree on what counts as a file and which mtime a rewritten entry
+ * carries, rather than each answering from a second walk of its own.
+ */
+export async function newestMtime(
+  path: string,
+): Promise<{ files: number; bytes: number; newest?: number } | undefined> {
+  if (!existsSync(path)) return undefined
+
+  const walked: Walked = {
+    files: 0,
+    bytes: 0,
+    touched: GROWTH_WINDOWS.map(() => 0),
+  }
+  await walk(path, walked, Date.now())
+
+  return { files: walked.files, bytes: walked.bytes, newest: walked.newest }
+}
+
 const UNITS = ['B', 'K', 'M', 'G'] as const
 
 /**

package/standards/publish.md

@@ -40,7 +40,7 @@ This check is one of the two the destination rule above scopes. The reader insid
 
 A phase label is one way text names the board, and a path under a record root is the other. Both resolve for a reader holding this checkout and neither resolves for anyone else, so this check is the second one the destination rule scopes.
 
-Two shapes get past a reader scanning for a bare label. A code span quoting a label is still the label, so read a span whose whole content is one as a hit and leave a longer token inside a span alone, which is a fixture name rather than a reference. The second shape is a path under a record root, gitignored and therefore absent from every clone, so `.canon/review/feedback/` names a folder the remote's reader cannot open.
+Two shapes get past a reader scanning for a bare label. A code span quoting a label is still the label, so read a span whose whole content is one as a hit and leave a longer token inside a span alone, which is a fixture name rather than a reference. The second shape is a path under a record root, gitignored and therefore absent from every clone, so `.canon/feedback/` names a folder the remote's reader cannot open.
 
 Under the tracked `canon/` and `.claude/` folders there is no hit, since `canon/context/governance/rules.md` resolves everywhere. `.canon/` carries no such carve-out: one ignore line covers the root whole, so every path beneath it is a hit regardless of which folder names it.
 

package/standards/skill.md

@@ -210,7 +210,7 @@ Without this skill, a session <observed failure>, <observed failure>.
 ### Output and tuning
 
 - Skill success lines emit the full relative path from the project root (`<dir>/<file>`) for any file written, updated, or deleted. A bare filename names a file the reader cannot open. The `## Output` section of the project's instruction file sets the form that path takes, so a skill body states which path is emitted and leaves the form to that section.
-- Before a skill writes anything, decide whether the output is a deliverable the project keeps or a toolkit session record. A deliverable lands among the project's own tracked files. A session record lands under `.canon/`, in the named subfolder for its kind (`tasks/`, `plans/`, `review/`, `memory/`, `groundwork/`, `intake/`, `proposals/`, `diagrams/`, `teach/`, `ready/`, or `walkthroughs/`, with `tmp/` for scratch nothing else claims), never in a folder the body invents. `canon/ARCHITECTURE.md`'s per-folder decisions are the precedent for which kind takes which folder.
+- Before a skill writes anything, decide whether the output is a deliverable the project keeps or a toolkit session record. A deliverable lands among the project's own tracked files. A session record lands under `.canon/`, in the named subfolder for its kind (`tasks/`, `plans/`, `review/`, `memory/`, `groundwork/`, `intake/`, `proposals/`, `diagrams/`, `teach/`, `ready/`, `feedback/`, `picks/`, `evidence/`, `transcripts/`, or `walkthroughs/`, with `tmp/` for scratch nothing else claims), never in a folder the body invents. A `review/` writer names its file `<kind>-<slug>.md` and writes it flat, and an `evidence/` folder takes the next two-digit ordinal as `<nn>-<slug>/`, numbered in the order the folders first appeared. `canon/ARCHITECTURE.md`'s per-folder decisions are the precedent for which kind takes which folder.
 - Codify a skill's posted or generated output as a fenced template, and keep the body consistent with every capability the frontmatter description names.
 - When a skill gathers user input or pre-seeds a template, attach a concrete proposed default to every question, derived from project context. Accept "use defaults" as a bulk-confirm.
 - Separate correctness axes (routing, sourcing, escalation, decline) from shape axes (line count, formatting, variant sprawl) when tuning a skill. Tighten only on correctness regressions. Do not convert soft caps to hard caps for aesthetic drift when correctness passes.

package/tooling/claude/seeds/.claude/hooks/index-reminder.sh

@@ -44,9 +44,9 @@ key=$(printf '%s__%s' "$session" "$index" | tr -c 'A-Za-z0-9' '_')
 # root the project carries rather than creating a second one beside it.
 project="${CLAUDE_PROJECT_DIR:-.}"
 if [ -d "$project/.canon" ]; then
-  marker_dir="$project/.canon/tmp/index-reminder"
+  marker_dir="$project/.canon/tmp/hooks/index-reminder"
 else
-  marker_dir="$project/.claude/.tmp/index-reminder"
+  marker_dir="$project/.claude/.tmp/hooks/index-reminder"
 fi
 marker="$marker_dir/$key"
 [ -f "$marker" ] && exit 0

package/tooling/claude/seeds/.claude/hooks/pr-create-log.sh

@@ -43,9 +43,9 @@ esac
 # The log is scratch, so it follows the scratch folder to whichever record root
 # the project carries rather than creating a second one beside it.
 if [ -d "$root/.canon" ]; then
-  log_dir="$root/.canon/tmp/pr-create-log"
+  log_dir="$root/.canon/tmp/pr/log"
 else
-  log_dir="$root/.claude/.tmp/pr-create-log"
+  log_dir="$root/.claude/.tmp/pr/log"
 fi
 mkdir -p "$log_dir"
 session=$(printf '%s' "$input" | jq -r '.session_id // "unknown"')

package/tooling/claude/seeds/.claude/hooks/scratch-guard.sh

@@ -48,9 +48,9 @@ session=$(printf '%s' "$input" | jq -r '.session_id // "none"')
 key=$(printf '%s' "$session" | tr -c 'A-Za-z0-9' '_')
 project="${CLAUDE_PROJECT_DIR:-.}"
 if [ -d "$project/.canon" ]; then
-  marker_dir="$project/.canon/tmp/scratch-guard"
+  marker_dir="$project/.canon/tmp/hooks/scratch-guard"
 else
-  marker_dir="$project/.claude/.tmp/scratch-guard"
+  marker_dir="$project/.claude/.tmp/hooks/scratch-guard"
 fi
 marker="$marker_dir/$key"
 [ -f "$marker" ] && exit 0

package/tooling/claude/seeds/CLAUDE.md

@@ -1,6 +1,6 @@
 # Project
 
-[One-line description]
+[One or two line description]
 
 ## Context
 
@@ -13,13 +13,9 @@
 
 ## Commands
 
-- These conventions came from a toolkit with its own CLI. A rule or standard naming a command is naming that CLI, present only where this project installed it.
-- [Command to run before committing]. Full script reference in the development entry under `canon/context/`.
+- [Command to run before committing]
 
 ## Key paths
 
 - `src/`: [description]
 - `canon/DESIGN.md`: design tokens and the visual system
-- `canon/context/`: per-domain narrative (how a domain is structured, decisions, gotchas), indexed via `canon/context/index.md`
-- `canon/wireframes/`: per-surface regions and states loaded on demand, indexed via `canon/wireframes/index.md`
-- `canon/decisions/`: decision history a project doc points at, never loaded eagerly