Merge remote-tracking branch 'origin/qv2' into deleteSchemaRefToQ

resolving merge conflict

Author: ekang7

README.md

@@ -2,58 +2,11 @@
 
 ## Installation
 
-- **macOS**:
-  - **DMG**: [Download now](https://desktop-release.q.us-east-1.amazonaws.com/latest/Amazon%20Q.dmg)
-  - **HomeBrew**: ```brew install --cask amazon-q ```
-- **Linux**:
-  - [Ubuntu/Debian](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html#command-line-installing-ubuntu)
-  - [AppImage](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html#command-line-installing-appimage)
-  - [Alternative Linux builds](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html#command-line-installing-alternative-linux)
-
-## Contributing
-
-Thank you so much for considering to contribute to KIRO CLI.
-
-Before getting started, see our [contributing docs](CONTRIBUTING.md#security-issue-notifications).
-
-### Prerequisites
-
-- MacOS
-  - Xcode 13 or later
-  - Brew
-
-#### 1. Clone repo
-
-```shell
-git clone https://github.com/aws/amazon-q-developer-cli.git
+Please use this command to install kiro. 
+``` shell
+curl -fsSL https://cli.kiro.dev/install | bash
 ```
 
-#### 2. Install the Rust toolchain using [Rustup](https://rustup.rs):
-
-```shell
-curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
-rustup default stable
-rustup toolchain install nightly
-cargo install typos-cli
-```
-
-#### 3. Develop locally
-
-- To compile and run: `cargo run --bin chat_cli`.
-- To run tests: `cargo test`.
-- To run lints: `cargo clippy`.
-- To format rust files: `cargo +nightly fmt`.
-- To run subcommands: `cargo run --bin chat_cli -- {subcommand}`.
-  - Login would then be: `cargo run --bin chat_cli -- login`
-
-## Project Layout
-
-- [`chat_cli`](crates/chat-cli/) - the `kiro` CLI, allows users to interface with KIRO Developer from
-  the command line
-- [`scripts/`](scripts/) - Contains ops and build related scripts
-- [`crates/`](crates/) - Contains all rust crates
-- [`docs/`](docs/) - Contains technical documentation
-
 ## Security
 
 For security related concerns, see [here](SECURITY.md).

crates/chat-cli/src/cli/chat/tools/introspect.rs

@@ -81,7 +81,7 @@ impl Introspect {
         documentation.push_str("\n\n--- changelog (from feed.json) ---\n");
         // Include recent changelog entries from feed.json
         let feed = crate::cli::feed::Feed::load();
-        let recent_entries = feed.get_all_changelogs().into_iter().take(5).collect::<Vec<_>>();
+        let recent_entries = feed.get_all_changelogs().into_iter().take(1).collect::<Vec<_>>();
         for entry in recent_entries {
             documentation.push_str(&format!("\n## {} ({})\n", entry.version, entry.date));
             for change in &entry.changes {

docs/agent-file-locations.md

@@ -7,16 +7,16 @@ Agent configuration files can be placed in two different locations, allowing for
 Local agents are stored in the current working directory under:
 
 ```
-.amazonq/cli-agents/
+.kiro/agents/
 ```
 
 These agents are specific to the current workspace or project and are only available when running KIRO CLI from that directory or its subdirectories.
 
 **Example structure:**
 ```
 my-project/
-├── .amazonq/
-│       └── cli-agents/
+├── .kiro/
+│       └── agents/
 │           ├── dev-agent.json
 │           └── aws-specialist.json
 └── src/
@@ -28,16 +28,16 @@ my-project/
 Global agents are stored in your home directory under:
 
 ```
-~/.aws/amazonq/cli-agents/
+~/.kiro/agents/
 ```
 
-Note: For globally available agents, the `amazonq` directory is in the `.aws` folder. 
+Note: For globally available agents, the `agents` directory is in the `.kiro` folder. 
 
 These agents are available from any directory when using KIRO CLI.
 
 **Example structure:**
 ```
-~/.aws/amazonq/cli-agents/
+~/.kiro/agents/
 ├── general-assistant.json
 ├── code-reviewer.json
 └── documentation-writer.json
@@ -47,8 +47,8 @@ These agents are available from any directory when using KIRO CLI.
 
 When KIRO CLI looks for an agent, it follows this precedence order:
 
-1. **Local first**: Checks `.amazonq/cli-agents/` in the current working directory
-2. **Global fallback**: If not found locally, checks `~/.aws/amazonq/cli-agents/` in the home directory
+1. **Local first**: Checks `.kiro/agents/` in the current working directory
+2. **Global fallback**: If not found locally, checks `~/.kiro/agents/` in the home directory
 
 ## Naming Conflicts
 
@@ -79,8 +79,8 @@ The global agent with the same name will be ignored in favor of the local versio
 To create a local agent for your current project:
 
 ```bash
-mkdir -p .amazonq/cli-agents
-cat > .amazonq/cli-agents/project-helper.json << 'EOF'
+mkdir -p .kiro/agents
+cat > .kiro/agents/project-helper.json << 'EOF'
 {
   "description": "Helper agent for this specific project",
   "tools": ["fs_read", "fs_write", "execute_bash"],
@@ -95,8 +95,8 @@ EOF
 To create a global agent available everywhere:
 
 ```bash
-mkdir -p ~/.aws/amazonq/cli-agents
-cat > ~/.aws/amazonq/cli-agents/general-helper.json << 'EOF'
+mkdir -p ~/.kiro/agents
+cat > ~/.kiro/agents/general-helper.json << 'EOF'
 {
   "description": "General purpose assistant",
   "tools": ["*"],
@@ -107,4 +107,4 @@ EOF
 
 ## Directory Creation
 
-KIRO CLI will automatically create the global agents directory (`~/.aws/amazonq/cli-agents/`) if it doesn't exist. However, you need to manually create the local agents directory (`.amazonq/cli-agents/`) in your workspace if you want to use local agents.
+KIRO CLI will automatically create the global agents directory (`~/.kiro/agents/`) if it doesn't exist. However, you need to manually create the local agents directory (`.kiro/agents/`) in your workspace if you want to use local agents.

docs/built-in-tools.md

@@ -127,7 +127,7 @@ This tool has no configuration options.
 
 ## TODO List Tool (experimental)
 
-Create and manage TODO lists for tracking multi-step tasks. Lists are stored locally in `.amazonq/cli-todo-lists/`.
+Create and manage TODO lists for tracking multi-step tasks. Lists are stored locally in `.kiro/cli-todo-lists/`.
 
 This tool has no configuration options.
 

docs/experiments.md

@@ -147,7 +147,7 @@ The summary is automatically added to your conversation context, so you can ask
 - Only one task can run per agent at a time
 
 **Task Storage:**
-Task execution details are stored in `.amazonq/.subagents/` in your current directory. Files persist until the same agent runs a new task.
+Task execution details are stored in `.kiro/.subagents/` in your current directory. Files persist until the same agent runs a new task.
 
 **Settings:**
 - `chat.enableDelegate` - Enable/disable delegate feature (boolean)
@@ -162,7 +162,7 @@ Task execution details are stored in `.amazonq/.subagents/` in your current dire
 **Features:**
 - Q will automatically make TODO lists when appropriate or when asked
 - View, manage, and delete TODOs using `/todos`
-- Resume existing TODO lists stored in `.amazonq/cli-todo-lists`
+- Resume existing TODO lists stored in `.kiro/cli-todo-lists`
 
 **Usage:**
 ```

docs/todo-lists.md

@@ -39,7 +39,7 @@ Delete specific TODO lists or all lists at once.
 
 ## Storage
 
-TODO lists are stored locally in `.amazonq/cli-todo-lists/` directory within your current working directory. Each list is saved as a JSON file with:
+TODO lists are stored locally in `.kiro/cli-todo-lists/` directory within your current working directory. Each list is saved as a JSON file with:
 
 - Unique timestamp-based ID
 - Task descriptions and completion status  
@@ -81,14 +81,14 @@ All commands use interactive selection allowing you to:
 If commands show "No to-do lists available":
 
 1. **Check directory**: Ensure you're in the directory where lists were created
-2. **Verify storage**: Look for `.amazonq/cli-todo-lists/` directory
+2. **Verify storage**: Look for `.kiro/cli-todo-lists/` directory
 3. **Create lists**: Use chat sessions to create new TODO lists
 
 #### Lists Not Loading
 
 If lists exist but won't load:
 
-1. **Check permissions**: Ensure read access to `.amazonq/cli-todo-lists/`
+1. **Check permissions**: Ensure read access to `.kiro/cli-todo-lists/`
 2. **Verify format**: Lists should be valid JSON files
 3. **Check file integrity**: Corrupted files may prevent loading