Check if this issue is valid — if so, understand the root cause and fix it. At src/features/claude-code-plugin-loader/loader.ts, line 467:

<comment>Wrapping synchronous functions in `Promise.resolve()` provides no parallelization benefit. Since `loadPluginCommands`, `loadPluginSkillsAsCommands`, `loadPluginAgents`, and `loadPluginHooksConfigs` are all synchronous, they still execute sequentially when called as arguments. Consider keeping the original sequential pattern for the sync functions and only `await` the async `loadPluginMcpServers`.</comment>

<file context>
@@ -464,11 +464,13 @@ export interface PluginComponentsResult {
-  const agents = loadPluginAgents(plugins)
-  const mcpServers = await loadPluginMcpServers(plugins)
-  const hooksConfigs = loadPluginHooksConfigs(plugins)
+  const [commands, skills, agents, mcpServers, hooksConfigs] = await Promise.all([
+    Promise.resolve(loadPluginCommands(plugins)),
+    Promise.resolve(loadPluginSkillsAsCommands(plugins)),
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/context-injector/injector.ts, line 129:

<comment>Using `Date.now()` alone for ID generation can cause collisions if called multiple times within the same millisecond. Consider using `crypto.randomUUID()` or combining timestamp with a random component.</comment>

<file context>
@@ -0,0 +1,166 @@
+        path?: { cwd?: string; root?: string }
+      }
+
+      const syntheticMessageId = `synthetic_ctx_${Date.now()}`
+      const syntheticPartId = `synthetic_ctx_part_${Date.now()}`
+      const now = Date.now()
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/context-injector/injector.test.ts, line 203:

<comment>Test helper `createMockMessage` generates inconsistent mock data: `messageID` in parts doesn&#39;t match `info.id`. The `info.id` includes `Math.random()` while `messageID` uses a separate `Date.now()` call without it, causing a mismatch. Consider storing the generated ID in a variable and reusing it.</comment>

<file context>
@@ -0,0 +1,292 @@
+      {
+        id: `part_${Date.now()}`,
+        sessionID,
+        messageID: `msg_${Date.now()}`,
+        type: &quot;text&quot; as const,
+        text,
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/opencode-skill-loader/blocking.ts, line 27:

<comment>Missing try/finally for resource cleanup. If an exception occurs after the Worker is created (e.g., in `postMessage` or `receiveMessageOnPort`), `worker.terminate()` and `port1.close()` will never be called, causing a resource leak.</comment>

<file context>
@@ -0,0 +1,62 @@
+  const signal = new Int32Array(new SharedArrayBuffer(4))
+  const { port1, port2 } = new MessageChannel()
+  
+  const worker = new Worker(new URL(&quot;./discover-worker.ts&quot;, import.meta.url), {
+    workerData: { signal }
+  })
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/claude-code-command-loader/loader.ts, line 190:

<comment>Template literal has extra leading spaces compared to sync version. Each content line has an unwanted leading space that will cause inconsistent command template output between `loadCommandsFromDir` and `loadCommandsFromDirAsync`.</comment>

<file context>
@@ -129,3 +130,130 @@ export function loadOpencodeProjectCommands(): Record&lt;string, CommandDefinition&gt;
+      const { data, body } = parseFrontmatter&lt;CommandFrontmatter&gt;(content)
+
+      const wrappedTemplate = `&lt;command-instruction&gt;
+ ${body.trim()}
+ &lt;/command-instruction&gt;
+
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/shared/opencode-config-dir.test.ts, line 221:

<comment>This assertion is too weak and doesn&#39;t match the test name. The test claims to verify &#39;returns null when no config exists&#39; but the assertion accepts both `null` and `string`, meaning it can never fail. Consider using a deterministic assertion that actually verifies the expected behavior.</comment>

<file context>
@@ -0,0 +1,224 @@
+      const result = detectExistingConfigDir(&quot;opencode&quot;, &quot;1.0.200&quot;)
+
+      // #then result is either null or a valid string path
+      expect(result === null || typeof result === &quot;string&quot;).toBe(true)
+    })
+  })
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/lint-workflows.yml, line 19:

<comment>Avoid downloading and executing remote scripts via `curl | bash` pattern. Consider using the official GitHub Action `rhysd/actionlint-action` instead, which is more secure and maintainable.</comment>

<file context>
@@ -0,0 +1,22 @@
+
+      - name: Install actionlint
+        run: |
+          bash &lt;(curl -sSL https://raw.githubusercontent.com/rhysd/actionlint/v1.7.10/scripts/download-actionlint.bash)
+
+      - name: Run actionlint
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/skill-mcp-manager/manager.ts, line 184:

<comment>`disconnectAll()` should also clear `pendingConnections` to fully reset manager state and avoid returning stale in-flight connections.</comment>

<file context>
@@ -102,26 +164,64 @@ export class SkillMcpManager {
 
   async disconnectAll(): Promise&lt;void&gt; {
-    for (const [, managed] of this.clients.entries()) {
+    this.stopCleanupTimer()
+    const clients = Array.from(this.clients.values())
+    this.clients.clear()
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At src/features/skill-mcp-manager/manager.ts, line 200:

<comment>Handle the Promise returned by `cleanupIdleClients()` in the interval callback to avoid unhandled rejections (and consider preventing overlapping runs if cleanup can take a while).</comment>

<file context>
@@ -102,26 +164,64 @@ export class SkillMcpManager {
+  private startCleanupTimer(): void {
+    if (this.cleanupInterval) return
+    this.cleanupInterval = setInterval(() =&gt; {
+      this.cleanupIdleClients()
+    }, 60_000)
+    this.cleanupInterval.unref()
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At .github/workflows/sisyphus-agent.yml, line 322:

<comment>`TITLE` is written to `$GITHUB_OUTPUT` with a plain `echo &quot;name=$value&quot;`, which is unsafe/brittle for untrusted text and can break or inject outputs if the title contains newlines/control characters. Use the delimiter (`&lt;&lt;EOF`) form (and quote `$GITHUB_OUTPUT`) when setting outputs.</comment>

<file context>
@@ -244,14 +309,17 @@ jobs:
               echo &quot;type=issue&quot; &gt;&gt; $GITHUB_OUTPUT
               echo &quot;number=${ISSUE_NUM}&quot; &gt;&gt; $GITHUB_OUTPUT
             fi
+            echo &quot;title=${TITLE}&quot; &gt;&gt; $GITHUB_OUTPUT
           fi
 
</file context>