snipara-companion 3.0.4 → 3.0.5

package/dist/index.js

@@ -10941,8 +10941,12 @@ function completeTeamSyncWorkFromEvidence(state, options = {}) {
   const workflowGoalText = normalizeCompletionText(options.workflowGoal);
   const summaryText = normalizeCompletionText(options.summary);
   const evidenceFiles = normalizeFiles(options.files);
-  const candidates = state.work.filter(
-    (item) => item.status === "active" && matchesCompletionEvidence(item, { workflowGoalText, summaryText, files: evidenceFiles })
+  const activeCandidates = state.work.filter((item) => item.status === "active");
+  const directCandidates = activeCandidates.filter(
+    (item) => matchesDirectCompletionEvidence(item, { workflowGoalText, summaryText })
+  );
+  const candidates = directCandidates.length > 0 ? directCandidates : activeCandidates.filter(
+    (item) => matchesCompletionEvidence(item, { workflowGoalText, summaryText, files: evidenceFiles })
   );
   if (!options.dryRun) {
     for (const item of candidates) {
@@ -12224,6 +12228,9 @@ function resolveRootDir(dir) {
   return path15.resolve(dir ?? process.cwd());
 }
 function matchesCompletionEvidence(item, evidence) {
+  if (matchesDirectCompletionEvidence(item, evidence)) {
+    return true;
+  }
   const itemText = normalizeCompletionText(item.summary);
   if (!itemText) {
     return false;
@@ -12231,16 +12238,23 @@ function matchesCompletionEvidence(item, evidence) {
   const evidenceTexts = [evidence.workflowGoalText, evidence.summaryText].filter(
     (value) => Boolean(value)
   );
-  if (evidenceTexts.some((text) => completionTextsMatch(itemText, text))) {
-    return true;
-  }
-  if (evidence.workflowGoalText) {
+  if (!teamSyncFilesOverlap(item.files, evidence.files)) {
     return false;
   }
-  if (!teamSyncFilesOverlap(item.files, evidence.files)) {
+  return evidenceTexts.some((text) => significantTokenOverlap(itemText, text));
+}
+function matchesDirectCompletionEvidence(item, evidence) {
+  const itemText = normalizeCompletionText(item.summary);
+  if (!itemText) {
     return false;
   }
-  return Boolean(evidence.summaryText && significantTokenOverlap(itemText, evidence.summaryText));
+  const evidenceTexts = [evidence.workflowGoalText, evidence.summaryText].filter(
+    (value) => Boolean(value)
+  );
+  if (evidenceTexts.some((text) => completionTextsMatch(itemText, text))) {
+    return true;
+  }
+  return false;
 }
 function normalizeCompletionText(value) {
   const normalized = value?.toLowerCase().replace(/[^a-z0-9]+/g, " ").replace(/\s+/g, " ").trim();

package/docs/FULL_REFERENCE.md

@@ -232,7 +232,10 @@ longer timeout, retries once with a shorter summary on transient hosted failures
 and then records a local fallback handoff in `.snipara/team-sync/session.json`
 if the hosted call still times out. A hosted final-commit timeout does not modify
 Git state. Custom final-commit categories are namespaced under `final-commit`
-before the hosted call so they stay on the handoff-only path.
+before the hosted call so they stay on the handoff-only path. Completed workflow
+commits also reconcile local Team Sync work: exact goal/summary matches close
+directly, and slug-like workflow goals can still close the matching active work
+when touched files overlap and meaningful workflow tokens match.
 
 ## Adaptive Work Routing
 
@@ -961,6 +964,7 @@ Semantics:
 - `snipara-companion workflow phase-start` = marks the current phase and prints the required Snipara context gate plus code-impact / symbol-card gates; runtime-marked phases also get a stable Snipara Sandbox session binding
 - `snipara-companion workflow runtime-checkpoint` = captures a resume-ready Snipara Sandbox checkpoint for one phase using local workflow state plus a hosted automation event when configured
 - `snipara-companion workflow phase-commit` = calls hosted `snipara_end_of_task_commit` for that phase, updates local state, and advances the next phase; if the hosted commit times out or hits a transient network failure, local workflow state still advances with an explicit local fallback record
+- `snipara-companion workflow phase-commit` and `workflow final-commit` also complete matching local Team Sync active work when the workflow is completed. Matching is conservative: exact workflow goal/summary text wins, and file overlap plus meaningful token overlap handles slug-like workflow goals without closing unrelated active work.
 - `snipara-companion workflow impact-gate` = local pre-push gate for completed workflow phases in `upstream..HEAD`; it keeps dirty files out of the committed impact analysis and reports phase/file coverage before hosted reindex catches up
 - `snipara-companion workflow resume` = reloads local workflow state plus hosted durable memory after compaction or resume, optionally includes short-lived session context with `--include-session-context`, then appends the latest hosted Team Sync handoff/checkpoint context when available; runtime-bound phases also print a Snipara Sandbox reattach or rehydrate plan; rerun `workflow phase-start` before editing again
 - `snipara-companion workflow resume` does not snapshot or exactly restore a live Snipara Sandbox process; exact process restore remains a roadmap item

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "snipara-companion",
-  "version": "3.0.4",
+  "version": "3.0.5",
   "description": "Local-first CLI that asks your repo what breaks before an AI coding agent edits it.",
   "main": "dist/index.js",
   "bin": {