chore: migrate boomtick-pkg (fixes #2988)

[arii]

This PR completes the monorepo restructuring to group boomtick-mcp and dev-tools under the self-contained boomtick-pkg/ directory, closing #2988.

Completed Tasks

• Relocated boomtick-mcp and dev-tools under boomtick-pkg/
• Restructured Python tools and updated ESM path definitions
• Synced self-healing.yml, ai-chatops.yml, and ci.yml with the triggers from PR 3010
• Updated lockfile and tested compatibility with frozen-lockfile
• Verified node (24.16.0) and pnpm (10.28.2) runtime versions

[github-actions]

🚀 Deployment Details (Last updated: Jun 26, 2026, 2:48 PM PST)

🚀 Pushed to gh-pages; publish in progress

• Preview URL: https://arii.github.io/tech-dancer/arii/feat-migration/
• Preview Dashboard: https://arii.github.io/tech-dancer/previews/index.html
• Commit SHA: baa3a7b
• Marker File: verify here

[arii]

🤖 AI Technical Audit

ANTI-AI-SLOP

This Pull Request demonstrates a strong commitment to anti-slop principles by significantly refactoring and consolidating critical workflow logic into reusable GitHub Actions within boomtick-pkg/mcp/actions. This move is excellent, eliminating substantial duplication across .github/workflows/ai-chatops.yml, .github/workflows/ci.yml, and .github/workflows/self-healing.yml. The centralization of Python development tools under boomtick-pkg/cli and the corresponding path updates across the repository (e.g., .agent-context.json, .devcontainer/, .githooks/, .github/PULL_REQUEST_REVIEW_TEMPLATE.md, package.json scripts) are well-executed. The updates to the project_config section within .agent-context.json also suggest a beneficial move towards more centralized and consistent configuration.

The overall direction of this PR—to modularize and centralize core tooling—is a significant architectural improvement that reduces technical debt and improves maintainability.

FINAL RECOMMENDATION (Approved with Minor Changes)

The overall architectural direction of this PR is highly approved. The consolidation of workflow logic into reusable actions and the centralized boomtick-pkg/ directory structure are substantial improvements. However, the current PR is failing CI checks and introduces two significant changes in ci.yml that require immediate attention and justification before full approval can be granted.

DEFINITION OF DONE

1. Resolve All CI Failures: Ensure all CI checks (validate, build, analyze, etc.) pass consistently.
2. Restore ci.yml Path Filters: Re-introduce specific paths triggers to ci.yml for both push and pull_request events, or provide a detailed justification for why the workflow should run on any file change, along with a plan to mitigate increased CI costs and feedback latency.
3. Justify ci.yml Permission Escalation: Provide a clear justification for the increased contents: write and checks: write permissions in ci.yml. If these are not strictly necessary, reduce them to the minimum required. Document why these permissions are needed for the ci-validate action's operation.
4. Justify knip --exclude exports: Explain why pnpm exec knip --exclude exports was added to the audit:dead-code script. Clarify if this exclusion is standard practice for the project's monorepo setup or if it intentionally allows certain dead code exports.

Review automatically published via RepoAuditor.