peaks-cli 1.2.1 → 1.2.3

package/dist/src/cli/commands/core-artifact-commands.js

@@ -274,8 +274,13 @@ export function registerCoreAndArtifactCommands(program, io) {
         .description('Extract stable project memory from skill artifacts into project .peaks/memory')
         .requiredOption('--project <path>', 'target project root')
         .requiredOption('--artifact <path...>', 'skill artifact paths inside the project')
-        .option('--dry-run', 'preview writes without changing files', true)
+        .option('--dry-run', 'preview writes without changing files')
         .option('--apply', 'write extracted memories into project .peaks/memory')).action((options) => {
+        if (options.dryRun === true && options.apply === true) {
+            printResult(io, fail('memory.extract', 'INVALID_MEMORY_EXTRACT_FLAGS', 'Use either --dry-run or --apply, not both', {}, ['Run without --apply to preview writes, or pass --apply to write memories']), options.json);
+            process.exitCode = 1;
+            return;
+        }
         try {
             const result = executeProjectMemoryExtract({ projectRoot: options.project, artifactPaths: options.artifact, apply: options.apply === true });
             printResult(io, ok('memory.extract', summarizeProjectMemoryExtractResult(result)), options.json);
@@ -290,8 +295,13 @@ export function registerCoreAndArtifactCommands(program, io) {
         .description('Back up project .peaks/memory into the artifact workspace')
         .requiredOption('--project <path>', 'target project root')
         .requiredOption('--workspace <path>', 'artifact workspace path')
-        .option('--dry-run', 'preview copies without changing files', true)
+        .option('--dry-run', 'preview copies without changing files')
         .option('--apply', 'copy project .peaks/memory into artifact workspace backup')).action((options) => {
+        if (options.dryRun === true && options.apply === true) {
+            printResult(io, fail('memory.sync', 'INVALID_MEMORY_SYNC_FLAGS', 'Use either --dry-run or --apply, not both', {}, ['Run without --apply to preview copies, or pass --apply to back up memories']), options.json);
+            process.exitCode = 1;
+            return;
+        }
         try {
             const result = executeProjectMemoryBackup({ projectRoot: options.project, artifactWorkspacePath: options.workspace, apply: options.apply === true });
             printResult(io, ok('memory.sync', summarizeProjectMemoryBackupResult(result)), options.json);

package/dist/src/shared/version.d.ts

@@ -1 +1 @@
-export declare const CLI_VERSION = "1.2.1";
+export declare const CLI_VERSION = "1.2.3";

package/dist/src/shared/version.js

@@ -1 +1 @@
-export const CLI_VERSION = "1.2.1";
+export const CLI_VERSION = "1.2.3";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "peaks-cli",
-  "version": "1.2.1",
+  "version": "1.2.3",
   "description": "Peaks CLI and short skill family for Claude Code automation.",
   "author": "SquabbyZ",
   "license": "MIT",

package/skills/peaks-rd/SKILL.md

@@ -89,6 +89,20 @@ peaks codegraph affected --project <repo> <changed-files...> --json
 #   - component library (antd, MUI, shadcn, etc.) and version
 #   - CSS solution (Less, Sass, TailwindCSS, CSS-in-JS) and conflicts
 #   - state management, routing, data fetching libraries
+#
+# After writing project-scan, embed durable memory markers for stable project facts.
+# Append one <!-- peaks-memory:start --> block per fact at the end of project-scan.md:
+#
+#   <!-- peaks-memory:start -->
+#   title: <component library>
+#   kind: module
+#   ---
+#   <Library> <version> — detected from package.json and source imports.
+#   <!-- peaks-memory:end -->
+#
+# Embed markers for: component library, CSS solution, build tool, state management,
+# routing, data fetching, and any legacy constraints. These facts are session-invariant
+# and valuable for future sessions. Do NOT embed secrets, credentials, or transient state.
 
 # 4.2 component library detection — verify against package.json, not assumptions
 # WRONG: "looks like a React project, let me use shadcn/ui"

package/skills/peaks-solo/SKILL.md

@@ -761,8 +761,11 @@ peaks sc boundary --slice-id <rid> --artifact <artifact> --code <file> --json
 peaks openspec validate <cid> --project <repo> --json
 peaks openspec archive <cid> --project <repo> --apply --json
 
-# 10. Peaks-Cli TXT handoff
-peaks memory extract --project <repo> --artifact <qa-artifact> --dry-run --json
+# 10. Peaks-Cli TXT handoff — invoke peaks-txt which embeds memory markers and extracts
+#     peaks-txt writes the handoff capsule to .peaks/<id>/txt/handoff.md with embedded
+#     <!-- peaks-memory:start --> blocks, then runs memory extract on it.
+#     --apply is REQUIRED to write .peaks/memory; without it the command only previews.
+peaks memory extract --project <repo> --artifact .peaks/<id>/txt/handoff.md --apply --json
 
 # 11. Peaks-Cli Final snapshot
 peaks project dashboard --project <repo> --json

package/skills/peaks-txt/SKILL.md

@@ -118,7 +118,7 @@ Stable memory body.
 <!-- peaks-memory:end -->
 ```
 
-The primary write target is the target project's `.peaks/memory`. Use `peaks memory extract --project <path> --artifact <artifact> --apply` only after the user or active profile allows durable project memory writes.
+The primary write target is the target project's `.peaks/memory`. Use `peaks memory extract --project <path> --artifact <artifact> --apply` to write durable project memories; omit `--apply` to preview without writing.
 
 ## Matt Pocock skills integration
 
@@ -190,13 +190,28 @@ peaks understand show --project <repo> --json
 # 4. Discover external capabilities before recommending memory or context tools
 peaks capabilities --json
 
-# 5. Memory extraction — dry-run by default, apply only when authorized
-peaks memory extract --project <repo> --artifact <artifact-path> --dry-run --json
-peaks memory extract --project <repo> --artifact <artifact-path> --apply --json
+# 5. Write the handoff capsule (see template above), then embed memory markers
+#    For each stable project fact, decision, rule, or convention discovered this session,
+#    append a <!-- peaks-memory:start --> block inside the capsule body:
+#
+#    <!-- peaks-memory:start -->
+#    title: Short project memory title
+#    kind: project | decision | convention | rule | reference | module
+#    ---
+#    Stable memory body. Concrete facts only — no secrets, no transient state.
+#    <!-- peaks-memory:end -->
+#
+#    Mark ONLY facts that survive the session: architectural decisions, stack constraints,
+#    naming conventions, API patterns, approved refactors. Do NOT embed: secrets, credentials,
+#    transient debugging notes, or session-specific context.
+
+# 6. Memory extraction — --apply is REQUIRED to write .peaks/memory
+#    (without --apply the command only previews; the directory will NOT be created)
+peaks memory extract --project <repo> --artifact .peaks/<id>/txt/handoff.md --apply --json
 peaks skill presence:clear --project <repo>                      # handoff capsule complete, remove presence indicator
 ```
 
-The final `--apply` call requires explicit user or profile authorization. Without it, keep the capsule under `.peaks/<session-id>/txt/` and reference artifact paths from other roles instead of duplicating their content.
+`peaks memory extract --apply` writes to `.peaks/memory` (without `--apply` it only previews). The handoff capsule `.peaks/<id>/txt/handoff.md` is the primary artifact for extraction — embed `<!-- peaks-memory:start -->` blocks in it for stable project facts before running extract.
 
 ### Transition verification gates (MANDATORY — run the command, see the output)