@fingerskier/augment 0.5.0 → 0.5.1

package/dist/pi/extension.js

@@ -90,29 +90,29 @@ async function gatherProjectContext(deps, query, cwd, projectNameOverride) {
     return sections.join("\n\n");
 }
 function augmentSystemPrompt(projectName) {
-    return `
-## Augment Memory Autopilot
-
-Augment is available through Pi tools named \`augment_*\`. Current project name: \`${projectName}\`.
-
-For non-trivial coding, bug fixing, refactoring, migration, architecture/spec, or test work:
-1. At task start, use injected Augment memory if present. If context was not injected or looks stale, call \`augment_project_context\` with the user's task and project_name=\`${projectName}\`.
-2. Before changing tracked behavior or files, call \`augment_search\` with the file path, component, command, error, or behavior to find related specs, issues, architecture decisions, and prior work.
-3. Before the final response, persist meaningful completed work with \`augment_upsert\`; call \`augment_init_project\` first if you need the current project_id.
-4. Link related memories with \`augment_link\` when a clear relationship exists.
-5. Do not store secrets, credentials, tokens, private keys, huge logs, dependency dumps, generated files, or full source files.
-6. Numeric memory IDs are local handles. Relative memory paths are the durable identity across rebuilds and machines.
+    return `
+## Augment Memory Autopilot
+
+Augment is available through Pi tools named \`augment_*\`. Current project name: \`${projectName}\`.
+
+For non-trivial coding, bug fixing, refactoring, migration, architecture/spec, or test work:
+1. At task start, use injected Augment memory if present. If context was not injected or looks stale, call \`augment_project_context\` with the user's task and project_name=\`${projectName}\`.
+2. Before changing tracked behavior or files, call \`augment_search\` with the file path, component, command, error, or behavior to find related specs, issues, architecture decisions, and prior work.
+3. Before the final response, persist meaningful completed work with \`augment_upsert\`; call \`augment_init_project\` first if you need the current project_id.
+4. Link related memories with \`augment_link\` when a clear relationship exists.
+5. Do not store secrets, credentials, tokens, private keys, huge logs, dependency dumps, generated files, or full source files.
+6. Numeric memory IDs are local handles. Relative memory paths are the durable identity across rebuilds and machines.
 `;
 }
 function persistencePrompt(projectName, summary) {
-    return `[augment] Persist meaningful completed work for project_name="${projectName}".
-
-1. Call augment_init_project with project_name="${projectName}" and keep the returned project_id.
-2. Identify distinct durable outcomes from this Pi session: requirements/specs, architecture decisions, bugs/risks, deferred TODOs, completed implementation WORK, and verification/test lessons.
-3. Call augment_search first to avoid duplicates; update an existing memory when appropriate.
-4. Call augment_upsert for each focused memory and augment_link for clear relationships.
-5. Summarize what was persisted and what remains open.
-
+    return `[augment] Persist meaningful completed work for project_name="${projectName}".
+
+1. Call augment_init_project with project_name="${projectName}" and keep the returned project_id.
+2. Identify distinct durable outcomes from this Pi session: requirements/specs, architecture decisions, bugs/risks, deferred TODOs, completed implementation WORK, and verification/test lessons.
+3. Call augment_search first to avoid duplicates; update an existing memory when appropriate.
+4. Call augment_upsert for each focused memory and augment_link for clear relationships.
+5. Summarize what was persisted and what remains open.
+
 ${summary ? `User-provided summary:\n${summary}` : "Use the conversation and tool history as the source of truth."}`;
 }
 function looksNonTrivial(event) {