Enable log output for lock stale issues workflow

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/commands/commit-push-pr.md

@@ -1,19 +0,0 @@
----
-allowed-tools: Bash(git checkout --branch:*), Bash(git add:*), Bash(git status:*), Bash(git push:*), Bash(git commit:*), Bash(gh pr create:*)
-description: Commit, push, and open a PR
----
-
-## Context
-
-- Current git status: !`git status`
-- Current git diff (staged and unstaged changes): !`git diff HEAD`
-- Current branch: !`git branch --show-current`
-
-## Your task
-
-Based on the above changes:
-1. Create a new branch if on main
-2. Create a single commit with an appropriate message
-3. Push the branch to origin
-4. Create a pull request using `gh pr create`
-5. You have the capability to call multiple tools in a single response. You MUST do all of the above in a single message. Do not use any other tools or do anything else. Do not send any other text or messages besides these tool calls.

.claude/commands/dedupe.md

@@ -1,37 +0,0 @@
----
-allowed-tools: Bash(gh issue view:*), Bash(gh search:*), Bash(gh issue list:*), Bash(gh api:*), Bash(gh issue comment:*)
-description: Find duplicate GitHub issues
----
-
-Find up to 3 likely duplicate issues for a given GitHub issue.
-
-To do this, follow these steps precisely:
-
-1. Use an agent to check if the Github issue (a) is closed, (b) does not need to be deduped (eg. because it is broad product feedback without a specific solution, or positive feedback), or (c) already has a duplicates comment that you made earlier. If so, do not proceed.
-2. Use an agent to view a Github issue, and ask the agent to return a summary of the issue
-3. Then, launch 5 parallel agents to search Github for duplicates of this issue, using diverse keywords and search approaches, using the summary from #1
-4. Next, feed the results from #1 and #2 into another agent, so that it can filter out false positives, that are likely not actually duplicates of the original issue. If there are no duplicates remaining, do not proceed.
-5. Finally, comment back on the issue with a list of up to three duplicate issues (or zero, if there are no likely duplicates)
-
-Notes (be sure to tell this to your agents, too):
-
-- Use `gh` to interact with Github, rather than web fetch
-- Do not use other tools, beyond `gh` (eg. don't use other MCP servers, file edit, etc.)
-- Make a todo list first
-- For your comment, follow the following format precisely (assuming for this example that you found 3 suspected duplicates):
-
----
-
-Found 3 possible duplicate issues:
-
-1. <link to issue>
-2. <link to issue>
-3. <link to issue>
-
-If your issue is a duplicate, please close it and 👍 the existing issue instead.
-
-<sub>This issue will be automatically closed as a duplicate in 3 days if there are no additional comments. To prevent auto-closure, please 👎 this comment.</sub>
-
-🤖 Generated with [Claude Code](https://claude.ai/code)
-
----

.devcontainer/init-firewall.sh

@@ -2,9 +2,6 @@
 set -euo pipefail  # Exit on error, undefined vars, and pipeline failures
 IFS=$'\n\t'       # Stricter word splitting
 
-# 1. Extract Docker DNS info BEFORE any flushing
-DOCKER_DNS_RULES=$(iptables-save -t nat | grep "127\.0\.0\.11" || true)
-
 # Flush existing rules and delete existing ipsets
 iptables -F
 iptables -X
@@ -14,16 +11,6 @@ iptables -t mangle -F
 iptables -t mangle -X
 ipset destroy allowed-domains 2>/dev/null || true
 
-# 2. Selectively restore ONLY internal Docker DNS resolution
-if [ -n "$DOCKER_DNS_RULES" ]; then
-    echo "Restoring Docker DNS rules..."
-    iptables -t nat -N DOCKER_OUTPUT 2>/dev/null || true
-    iptables -t nat -N DOCKER_POSTROUTING 2>/dev/null || true
-    echo "$DOCKER_DNS_RULES" | xargs -L 1 iptables -t nat
-else
-    echo "No Docker DNS rules to restore"
-fi
-
 # First allow DNS and localhost before any restrictions
 # Allow outbound DNS
 iptables -A OUTPUT -p udp --dport 53 -j ACCEPT

.github/workflows/auto-close-duplicates.yml

@@ -1,78 +0,0 @@
-name: Auto-close duplicate issues (DRY RUN)
-description: Dry run - logs issues that would be auto-closed as duplicates after 3 days if no response
-on:
-  schedule:
-    - cron: '0 9 * * *'
-
-jobs:
-  auto-close-duplicates:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: read
-      issues: write
-
-    steps:
-      - name: Auto-close duplicate issues
-        uses: actions/github-script@v7
-        with:
-          script: |
-            const threeDaysAgo = new Date();
-            threeDaysAgo.setDate(threeDaysAgo.getDate() - 3);
-            
-            // Get all open issues
-            const { data: issues } = await github.rest.issues.listForRepo({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              state: 'open',
-              per_page: 100
-            });
-            
-            for (const issue of issues) {
-              // Get comments for this issue
-              const { data: comments } = await github.rest.issues.listComments({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: issue.number
-              });
-              
-              // Find duplicate comments (look for "Found 1 possible duplicate" or "Found X possible duplicate")
-              const dupeComments = comments.filter(comment => 
-                comment.body.includes('Found') && 
-                comment.body.includes('possible duplicate') &&
-                comment.user.type === 'Bot'
-              );
-              
-              if (dupeComments.length === 0) continue;
-              
-              // Get the most recent duplicate comment
-              const lastDupeComment = dupeComments[dupeComments.length - 1];
-              const dupeCommentDate = new Date(lastDupeComment.created_at);
-              
-              // Check if the duplicate comment is 3+ days old
-              if (dupeCommentDate > threeDaysAgo) continue;
-              
-              // Check if there are any comments after the duplicate comment
-              const commentsAfterDupe = comments.filter(comment => 
-                new Date(comment.created_at) > dupeCommentDate
-              );
-              
-              if (commentsAfterDupe.length > 0) continue;
-              
-              // Check if issue author reacted with thumbs down to the duplicate comment
-              const { data: reactions } = await github.rest.reactions.listForIssueComment({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                comment_id: lastDupeComment.id
-              });
-              
-              const authorThumbsDown = reactions.some(reaction => 
-                reaction.user.id === issue.user.id && reaction.content === '-1'
-              );
-              
-              if (authorThumbsDown) continue;
-              
-              // DRY RUN: Log the issue that would be auto-closed
-              const issueUrl = `https://github.com/${context.repo.owner}/${context.repo.repo}/issues/${issue.number}`;
-              console.log(`[DRY RUN] Would auto-close issue #${issue.number} as duplicate: ${issueUrl}`);
-            }

.github/workflows/claude-dedupe-issues.yml

@@ -1,25 +0,0 @@
-name: Claude Issue Dedupe
-description: Automatically dedupe GitHub issues using Claude Code
-on:
-  issues:
-    types: [opened]
-
-jobs:
-  claude-dedupe-issues:
-    runs-on: ubuntu-latest
-    timeout-minutes: 10
-    permissions:
-      contents: read
-      issues: write
-
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-
-      - name: Run Claude Code slash command
-        uses: anthropics/claude-code-base-action@beta
-        with:
-          prompt: "/dedupe ${{ github.repository }}/issues/${{ github.event.issue.number }}"
-          anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
-          claude_env: |
-            GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/lock-closed-issues.yml

@@ -13,81 +13,16 @@ concurrency:
   group: lock-threads
 
 jobs:
-  lock-closed-issues:
+  lock-threads:
     runs-on: ubuntu-latest
-    timeout-minutes: 10
     steps:
-      - name: Lock closed issues after 7 days of inactivity
-        uses: actions/github-script@v7
+      - uses: dessant/lock-threads@1bf7ec25051fe7c00bdd17e6a7cf3d7bfb7dc771 # v5.0.1
         with:
-          script: |
-            const sevenDaysAgo = new Date();
-            sevenDaysAgo.setDate(sevenDaysAgo.getDate() - 7);
-            
-            const lockComment = `This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.`;
-            
-            let page = 1;
-            let hasMore = true;
-            let totalLocked = 0;
-            
-            while (hasMore) {
-              // Get closed issues (pagination)
-              const { data: issues } = await github.rest.issues.listForRepo({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                state: 'closed',
-                sort: 'updated',
-                direction: 'asc',
-                per_page: 100,
-                page: page
-              });
-              
-              if (issues.length === 0) {
-                hasMore = false;
-                break;
-              }
-              
-              for (const issue of issues) {
-                // Skip if already locked
-                if (issue.locked) continue;
-                
-                // Skip pull requests
-                if (issue.pull_request) continue;
-                
-                // Check if updated more than 7 days ago
-                const updatedAt = new Date(issue.updated_at);
-                if (updatedAt > sevenDaysAgo) {
-                  // Since issues are sorted by updated_at ascending, 
-                  // once we hit a recent issue, all remaining will be recent too
-                  hasMore = false;
-                  break;
-                }
-                
-                try {
-                  // Add comment before locking
-                  await github.rest.issues.createComment({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issue.number,
-                    body: lockComment
-                  });
-                  
-                  // Lock the issue
-                  await github.rest.issues.lock({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: issue.number,
-                    lock_reason: 'resolved'
-                  });
-                  
-                  totalLocked++;
-                  console.log(`Locked issue #${issue.number}: ${issue.title}`);
-                } catch (error) {
-                  console.error(`Failed to lock issue #${issue.number}: ${error.message}`);
-                }
-              }
-              
-              page++;
-            }
-            
-            console.log(`Total issues locked: ${totalLocked}`);
+          issue-inactive-days: "7"
+          process-only: "issues"
+          log-output: true
+          issue-comment: >
+            This issue has been automatically locked since it was
+            closed and has not had any activity for 7 days.
+            If you're experiencing a similar issue, please file a new issue
+            and reference this one if it's relevant.

CHANGELOG.md

@@ -1,42 +1,5 @@
 # Changelog
 
-## 1.0.70
-
-- Performance: Optimized message rendering for better performance with large contexts
-- Windows: Fixed native file search, ripgrep, and subagent functionality
-- Added support for @-mentions in slash command arguments
-
-## 1.0.69
-
-- Upgraded Opus to version 4.1
-
-## 1.0.68
-
-- Fix incorrect model names being used for certain commands like `/pr-comments`
-- Windows: improve permissions checks for allow / deny tools and project trust. This may create a new project entry in `.claude.json` - manually merge the history field if desired.
-- Windows: improve sub-process spawning to eliminate "No such file or directory" when running commands like pnpm
-- Enhanced /doctor command with CLAUDE.md and MCP tool context for self-serve debugging
-- SDK: Added canUseTool callback support for tool confirmation
-- Added `disableAllHooks` setting
-- Improved file suggestions performance in large repos
-
-## 1.0.65
-
-- IDE: Fixed connection stability issues and error handling for diagnostics
-- Windows: Fixed shell environment setup for users without .bashrc files
-
-## 1.0.64
-
-- Agents: Added model customization support - you can now specify which model an agent should use
-- Agents: Fixed unintended access to the recursive agent tool
-- Hooks: Added systemMessage field to hook JSON output for displaying warnings and context
-- SDK: Fixed user input tracking across multi-turn conversations
-- Added hidden files to file search and @-mention suggestions
-
-## 1.0.63
-
-- Windows: Fixed file search, @agent mentions, and custom slash commands functionality
-
 ## 1.0.62
 
 - Added @-mention support with typeahead for custom agents. @<your-custom-agent> to invoke it