chore: remove orphaned Amazon Q artifacts

[atxtechbro]

Summary

• Removed Amazon Q configuration and tooling artifacts (175 lines)
• Amazon Q was previously removed due to qterm shell hijacking issues

Changes

Deleted files:

• AmazonQ.md - Broken symlink to deleted AI-RULES.md
• .amazonq/global_context.json - Configuration for removed provider
• bin/add-amazonq - Script to create AmazonQ.md files
• templates/AmazonQ.md.template - Template for removed provider
• mcp/tests/AmazonQ.md - Test instructions for unused tool
• utils/configure-amazonq.sh - Configuration script

Context

From knowledge/principles/ai-provider-agnosticism.md:

"Amazon Q Removed: Through tracer bullet iteration, we discovered it hijacked shell sessions with qterm, breaking tmux. Removing it achieved better throughput - proving two providers are optimal."

Target file AI-RULES.md was deleted July 16, 2025 (commit 7fc7888), leaving all Amazon Q files orphaned.

Test plan

• Verify no references to removed files remain in codebase
• Confirm no functionality depends on Amazon Q tooling

Principle: subtraction-creates-value (part of spring cleanup series #1374-1379)

[amazon-q-developer]

⏳ Code review in progress. Analyzing for code quality issues and best practices. Detailed findings will be posted upon completion.

Using Amazon Q Developer for GitHub

Amazon Q Developer¹ is an AI-powered assistant that integrates directly into your GitHub workflow, enhancing your development process with intelligent features for code development, review, and transformation.

Slash Commands

Command	Description
/q <message>	Chat with the agent to ask questions or request revisions
/q review	Requests an Amazon Q powered code review
/q help	Displays usage information

Features

Agentic Chat
Enables interactive conversation with Amazon Q to ask questions about the pull request or request specific revisions. Use /q <message> in comment threads or the review body to engage with the agent directly.

Code Review
Analyzes pull requests for code quality, potential issues, and security concerns. Provides feedback and suggested fixes. Automatically triggered on new or reopened PRs (can be disabled for AWS registered installations), or manually with /q review slash command in a comment.

Customization

You can create project-specific rules for Amazon Q Developer to follow:

1. Create a .amazonq/rules folder in your project root.
2. Add Markdown files in this folder to define rules (e.g., cdk-rules.md).
3. Write detailed prompts in these files, such as coding standards or best practices.
4. Amazon Q Developer will automatically use these rules when generating code or providing assistance.

Example rule:

All Amazon S3 buckets must have encryption enabled, enforce SSL, and block public access.
All Amazon DynamoDB Streams tables must have encryption enabled.
All Amazon SNS topics must have encryption enabled and enforce SSL.
All Amazon SNS queues must enforce SSL.

Feedback

To provide feedback on Amazon Q Developer, create an issue in the Amazon Q Developer public repository.

For more detailed information, visit the Amazon Q for GitHub documentation.

Footnotes

1. Amazon Q Developer uses generative AI. You may need to verify generated code before using it in your environment. See the AWS Responsible AI Policy. ↩

[amazon-q-developer]

This is an excellent cleanup PR that properly removes orphaned Amazon Q artifacts following the "subtraction creates value" principle. The changes are well-documented and align perfectly with the context provided in knowledge/principles/ai-provider-agnosticism.md about Amazon Q being removed due to qterm shell hijacking issues.

Key Strengths:

• Complete cleanup: All 6 Amazon Q-related files are properly removed (175 lines deleted)
• Well-documented rationale: Clear explanation of why Amazon Q was removed and why these files became orphaned
• Consistent with codebase principles: Aligns with the documented AI provider agnosticism strategy
• No remaining references: I verified that no dangling references to Amazon Q remain in the main configuration files

Files Removed:

• Configuration: .amazonq/global_context.json
• Broken symlink: AmazonQ.md
• Tooling: bin/add-amazonq, utils/configure-amazonq.sh
• Templates and tests: templates/AmazonQ.md.template, mcp/tests/AmazonQ.md

The removal is justified by the documented issues with qterm hijacking tmux sessions, and the cleanup maintains the two-provider strategy (Claude Code + OpenAI Codex) that proved optimal for throughput. This PR successfully eliminates technical debt while maintaining system functionality.