synarcx 0.3.1 → 0.3.3

package/dist/core/migration.js

@@ -94,14 +94,14 @@ export function migrateIfNeeded(projectPath, tools) {
         // No workflows installed, new user — defaults will apply
         return;
     }
-    // Migrate: set profile to custom with detected workflows
-    config.profile = 'custom';
-    config.workflows = installedWorkflows;
+    // Migrate: pre-profile users had the full installed set — that maps to 'core'.
+    // Setting 'core' means they automatically receive every future new command
+    // (e.g. 'review', and anything added later) without any manual steps.
+    config.profile = 'core';
     if (rawConfig.delivery === undefined) {
         config.delivery = inferDelivery(artifacts);
     }
     saveGlobalConfig(config);
-    console.log(`Migrated: custom profile with ${installedWorkflows.length} workflows`);
-    console.log("New in this version: /syn:propose. Try 'synarcx config profile core' for the streamlined experience.");
+    console.log(`Migrated to core profile — you'll receive all future commands automatically.`);
 }
 //# sourceMappingURL=migration.js.map

package/dist/core/profiles.d.ts

@@ -4,12 +4,20 @@
  * Defines workflow profiles that control which workflows are installed.
  * Profiles determine WHICH workflows; delivery (in global config) determines HOW.
  */
-import type { Profile } from './global-config.js';
+import type { Profile, GlobalConfig } from './global-config.js';
 /**
  * Resolves which workflows should be active for a given profile configuration.
  *
  * - 'core' profile always returns CORE_WORKFLOWS
  * - 'custom' profile returns the provided customWorkflows, or empty array if not provided
  */
-export declare function getProfileWorkflows(profile: Profile, customWorkflows?: string[]): readonly string[];
+export declare function getProfileWorkflows(profile: Profile, customWorkflows?: readonly string[]): readonly string[];
+/**
+ * Ensures a 'custom' profile always contains all current ALL_WORKFLOWS entries.
+ * Called by both `synarcx init` and `synarcx update` so new commands (e.g. syn:review)
+ * are never silently dropped for users on a stale custom profile, regardless of which
+ * command they run after upgrading.
+ * No-op for 'core' profile (it derives its list from ALL_WORKFLOWS directly).
+ */
+export declare function syncNewCoreWorkflowsToCustomProfile(config: GlobalConfig): void;
 //# sourceMappingURL=profiles.d.ts.map

package/dist/core/profiles.js

@@ -4,7 +4,8 @@
  * Defines workflow profiles that control which workflows are installed.
  * Profiles determine WHICH workflows; delivery (in global config) determines HOW.
  */
-import { CORE_WORKFLOWS } from './shared/workflow-registry.js';
+import { saveGlobalConfig } from './global-config.js';
+import { ALL_WORKFLOWS, CORE_WORKFLOWS } from './shared/workflow-registry.js';
 /**
  * Resolves which workflows should be active for a given profile configuration.
  *
@@ -17,4 +18,22 @@ export function getProfileWorkflows(profile, customWorkflows) {
     }
     return CORE_WORKFLOWS;
 }
+/**
+ * Ensures a 'custom' profile always contains all current ALL_WORKFLOWS entries.
+ * Called by both `synarcx init` and `synarcx update` so new commands (e.g. syn:review)
+ * are never silently dropped for users on a stale custom profile, regardless of which
+ * command they run after upgrading.
+ * No-op for 'core' profile (it derives its list from ALL_WORKFLOWS directly).
+ */
+export function syncNewCoreWorkflowsToCustomProfile(config) {
+    if (config.profile !== 'custom')
+        return;
+    const current = config.workflows ?? [];
+    const currentSet = new Set(current);
+    const missing = ALL_WORKFLOWS.filter(w => !currentSet.has(w));
+    if (missing.length === 0)
+        return;
+    config.workflows = [...current, ...missing];
+    saveGlobalConfig(config);
+}
 //# sourceMappingURL=profiles.js.map

package/dist/core/shared/skill-generation.js

@@ -77,18 +77,18 @@ export function generateSkillContent(template, generatedByVersion, transformInst
     const instructions = transformInstructions
         ? transformInstructions(template.instructions)
         : template.instructions;
-    return `---
-name: ${template.name}
-description: ${template.description}
-license: ${template.license || 'MIT'}
-compatibility: ${template.compatibility || 'Requires synarcx CLI.'}
-metadata:
-  author: ${template.metadata?.author || 'synarcx'}
-  version: "${template.metadata?.version || '1.0'}"
-  generatedBy: "${generatedByVersion}"
----
-
-${instructions}
+    return `---
+name: ${template.name}
+description: ${template.description}
+license: ${template.license || 'MIT'}
+compatibility: ${template.compatibility || 'Requires synarcx CLI.'}
+metadata:
+  author: ${template.metadata?.author || 'synarcx'}
+  version: "${template.metadata?.version || '1.0'}"
+  generatedBy: "${generatedByVersion}"
+---
+
+${instructions}
 `;
 }
 //# sourceMappingURL=skill-generation.js.map

package/dist/core/specs-apply.js

@@ -270,7 +270,10 @@ export async function writeUpdatedSpec(update, rebuilt, counts) {
     // Create target directory if needed
     const targetDir = path.dirname(update.target);
     await fs.mkdir(targetDir, { recursive: true });
-    await fs.writeFile(update.target, rebuilt);
+    // Atomic write: write to .tmp then rename (prevents half-written files on crash)
+    const tmpPath = update.target + '.tmp';
+    await fs.writeFile(tmpPath, rebuilt);
+    await fs.rename(tmpPath, update.target);
     const specName = path.basename(path.dirname(update.target));
     console.log(`Applying changes to synspec/specs/${specName}/spec.md:`);
     if (counts.added)
@@ -347,10 +350,12 @@ export async function applySpecs(projectRoot, changeName, options = {}) {
     for (const p of prepared) {
         const capability = path.basename(path.dirname(p.update.target));
         if (!options.dryRun) {
-            // Write the updated spec
+            // Write the updated spec (atomic: .tmp + rename)
             const targetDir = path.dirname(p.update.target);
             await fs.mkdir(targetDir, { recursive: true });
-            await fs.writeFile(p.update.target, p.rebuilt);
+            const tmpPath = p.update.target + '.tmp';
+            await fs.writeFile(tmpPath, p.rebuilt);
+            await fs.rename(tmpPath, p.update.target);
             if (!options.silent) {
                 console.log(`Applying changes to synspec/specs/${capability}/spec.md:`);
                 if (p.counts.added)

package/dist/core/templates/workflows/debug.js

@@ -71,7 +71,7 @@ export function getSynDebugCommandTemplate() {
         name: 'syn:debug',
         description: 'Investigate a known error — root cause analysis through hypothesis, explicitly prompts /syn:propose',
         tags: ['workflow', 'debug', 'fix'],
-        content: `Investigate a known error or failure systematically in 3 phases. Produces a diagnosis and suggests \`/syn:propose\` for creating the fix change.
+        content: `Investigate a known error or failure systematically in 3 phases. Produces a diagnosis and explicitly prompts the user to run \`/syn:propose\` — does NOT auto-create artifacts or auto-hand off.
 
 **Input**: Error message, symptom, or failure description. The argument after \`/syn:debug\` is what went wrong.
 
@@ -79,7 +79,12 @@ export function getSynDebugCommandTemplate() {
 
 ## Initial Context
 
-If a change is active, read its artifacts first to understand what was intended vs. what went wrong.
+If a change is active, read its artifacts first:
+- \`synspec/changes/<name>/proposal.md\`
+- \`synspec/changes/<name>/design.md\`
+- \`synspec/changes/<name>/tasks.md\`
+
+Use that context to understand what was intended vs. what went wrong.
 
 ---
 
@@ -111,7 +116,19 @@ If a change is active, read its artifacts first to understand what was intended
 
 ## Output
 
-After completing, present the diagnosis and explicitly prompt the user to run \`/syn:propose\` to formalize the fix. Do NOT auto-create artifacts.`
+After completing the 3-phase investigation, present findings and prompt explicitly:
+
+\`\`\`
+### Diagnosis
+
+**Root Cause**: <what was found>
+**Pattern**: <similar issues or novel>
+**Hypothesis**: <proposed fix approach>
+
+**Ready to formalize?** Run \`/syn:propose\` to create a change with these findings.
+\`\`\`
+
+Do NOT create any artifacts, do NOT start the pipeline automatically. The user must explicitly run \`/syn:propose\` to formalize.`
     });
 }
 //# sourceMappingURL=debug.js.map

package/dist/core/templates/workflows/refactor.js

@@ -103,12 +103,52 @@ export function getSynRefactorCommandTemplate() {
 
 ---
 
+## Initial Context
+
+Check for existing context:
+\`\`\`bash
+synarcx list --json
+\`\`\`
+
+If a relevant change exists, read its artifacts. Otherwise, start fresh.
+
+---
+
+## Reframing the Problem
+
+This is a structural-change investigation. The goal is to improve code organization, reduce duplication, increase cohesion, or decrease coupling — without changing what the system does.
+
+### Opening Question
+
+Start by asking (use AskUserQuestion tool, open-ended):
+> "What part of the codebase feels like it needs restructuring?"
+
+Let the user describe the pain point before diving in.
+
+---
+
 ## Investigation
 
-1. **Map the current shape** — read relevant source files, identify module boundaries, dependencies, duplication.
-2. **Identify the target shape** — define what the ideal structure looks like.
-3. **Surface risks** — flag implicit dependencies, testing hazards, areas that could get worse.
-4. **Visualize** — use ASCII diagrams to show current vs. target structure.
+1. **Map the current shape** — read relevant source files, identify:
+   - Module boundaries and responsibilities
+   - Dependency direction
+   - Code duplication or overlapping concerns
+   - Testing patterns
+
+2. **Identify the target shape** — work with the user to define:
+   - What the ideal structure would look like
+   - Which modules or files move where
+   - How dependencies should flow
+
+3. **Surface risks** — flag areas of concern:
+   - Implicit dependencies that aren't visible in imports
+   - Areas where refactoring could make things worse
+   - Testing hazards (brittle tests, high coupling to internals)
+
+4. **Visualize** — use ASCII diagrams to show:
+   - Current vs. target module structure
+   - Dependency direction changes
+   - File/move relationships
 
 ---
 
@@ -120,7 +160,20 @@ When artifacts are created, the analyze phase MUST check for behavior contract v
 
 ## Hand-Off
 
-Present a summary with Current Shape, Target Shape, Key Changes, and Risks. Then explicitly prompt: "Ready to formalize? Run \`/syn:propose\` to create a change with these findings."`
+When the investigation reaches a clear conclusion, present findings and explicitly prompt:
+
+\`\`\`
+### Refactoring Plan
+
+**Current Shape**: <summary of current structure>
+**Target Shape**: <proposed structure>
+**Key Changes**: <list of structural moves>
+**Risks**: <potential issues>
+
+**Ready to formalize?** Run \`/syn:propose\` to create a change with these findings.
+\`\`\`
+
+Do NOT create any artifacts or start the pipeline. The user must explicitly run \`/syn:propose\`.`
     });
 }
 //# sourceMappingURL=refactor.js.map