opencode-swarm 7.8.1 → 7.10.0

package/dist/commands/archive.error-handling.test.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Tests for archive.ts graceful handling of corrupt evidence files (Task 1.6)
+ *
+ * Verifies that the try/catch in handleArchiveCommand's dry-run loop
+ * catches exceptions from loadEvidence and skips corrupt/unreadable files.
+ *
+ * Uses real filesystem operations like existing archive tests.
+ */
+export {};

package/dist/commands/benchmark.error-handling.test.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Tests for benchmark.ts graceful handling of corrupt evidence files.
+ *
+ * Verifies that the try/catch in handleBenchmarkCommand's cumulative loop
+ * catches exceptions from loadEvidence and skips corrupt/unreadable files.
+ */
+export {};

package/dist/commands/dark-matter.error-handling.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/handoff.error-handling.adversarial.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/handoff.error-handling.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/index.not-found.adversarial.test.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Adversarial security tests for command-not-found UX in createSwarmCommandHandler.
+ *
+ * Attack vectors covered:
+ * 1. Very long command name (10000+ chars) — does it hang or crash?
+ * 2. Command with special characters (script injection, shell injection, template literals)
+ * 3. Command with newlines/embedded control chars — does it break output format?
+ * 4. Command with unicode/emoji — handled gracefully?
+ * 5. Extremely deep tokens array (1000 elements) — does findSimilarCommands handle it?
+ * 6. Null bytes in command name
+ */
+export {};

package/dist/commands/index.not-found.test.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Tests for command-not-found UX improvement in createSwarmCommandHandler.
+ *
+ * Covers:
+ * - Unknown single-word command shows "Command not found" + suggestions + footer
+ * - Unknown compound command shows header with command name
+ * - Empty tokens (empty array) → returns buildHelpText() output
+ * - Command with no similar matches → shows header + footer only (no "Did you mean" section)
+ * - Multiple similar commands returned → all shown with bullet format
+ */
+export {};

package/dist/commands/registration-parity.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/registry.find-similar.adversarial.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/registry.find-similar.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/simulate.report-write.adversarial.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/commands/simulate.report-write.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/git/branch.d.ts

@@ -76,6 +76,24 @@ declare function detectDefaultRemoteBranch(cwd: string): string | null;
 export declare function resetToRemoteBranch(cwd: string, options?: {
     pruneBranches?: boolean;
 }): ResetToRemoteBranchResult;
+export interface ResetToMainAfterMergeResult {
+    success: boolean;
+    targetBranch: string;
+    previousBranch: string;
+    message: string;
+    branchDeleted: boolean;
+    changesDiscarded: boolean;
+    warnings: string[];
+}
+/**
+ * Aggressive git reset for post-merge cleanup.
+ * Handles the common scenario: feature branch PR merged, local has uncommitted artifacts.
+ * Steps: detect default branch → safety check → fetch → checkout → discard changes → reset → delete branch.
+ * Safety guard: refuses if current branch has commits not on any remote tracking branch.
+ */
+export declare function resetToMainAfterMerge(cwd: string, options?: {
+    pruneBranches?: boolean;
+}): ResetToMainAfterMergeResult;
 /**
  * DI seam for testability. Contains all test-mocked exports.
  * Internal calls should use _internals.fn() instead of fn() directly.
@@ -85,5 +103,6 @@ export declare const _internals: {
     detectDefaultRemoteBranch: typeof detectDefaultRemoteBranch;
     getDefaultBaseBranch: typeof getDefaultBaseBranch;
     resetToRemoteBranch: typeof resetToRemoteBranch;
+    resetToMainAfterMerge: typeof resetToMainAfterMerge;
 };
 export {};