ratatui_ruby 0.3.1 → 0.5.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6c258db0dbb30641f2813c23f6212a3e6e3ee56c8aa3b56a428e67d4b97bcae1
-  data.tar.gz: 7dbbec9b16667b25a148bff938ea3448611689f04dae722a24600d6ebc29d9ef
+  metadata.gz: 706f0da7ece6637bedb71da9ce2c3bd2b94c357f121fcfd305caa468a2e74637
+  data.tar.gz: 8f0e05bc53177c92a972f7badd9db952e3eb5856413b6b16bc7e41d106ba2652
 SHA512:
-  metadata.gz: 9d395bce840eb550abf6f91567c1ca1952c6b7e184749c3bd7db3188d71f97a9c876af535d71cf21606e28aa23e780f5294595b54baf1640620743d8de8ef664
-  data.tar.gz: 385435bf381ba2602f8e306c74cb8842416c1bb39100cd576abedf9c0cf3421c79d688a58abd1b8a1b4915caaae781288d490a02077f3fbc04a161b891583add
+  metadata.gz: abea59dfb0c71cff7779eee2af7766796a75d1e2499eac3cce40cf901f78ababa453caa1812c70ef44acb88c25a5bb02c9f4e8983d338b79c3b38946f624fd80
+  data.tar.gz: eb01c6a74f469487e782372a86911ae23b7841df1bd42b0820e5e7a9577d891ce3084ae1fb31b7cf3c35d5898e89c37d5fdb8d581b7fabedf52254fc21627be8

data/.builds/ruby-3.2.yml

@@ -1,22 +1,22 @@
 # SPDX-FileCopyrightText: 2025 Kerrick Long <me@kerricklong.com>
 # SPDX-License-Identifier: AGPL-3.0-or-later
 
-image: alpine/edge
+image: archlinux
 packages:
   - bash
-  - build-base
+  - base-devel
   - curl
-  - openssl-dev
-  - yaml-dev
-  - zlib-dev
-  - readline-dev
-  - gdbm-dev
-  - ncurses-dev
-  - libffi-dev
-  - clang-dev
+  - openssl
+  - libyaml
+  - zlib
+  - readline
+  - gdbm
+  - ncurses
+  - libffi
+  - clang
   - git
 artifacts:
-  - ratatui_ruby/pkg/ratatui_ruby-0.3.1.gem
+  - ratatui_ruby/pkg/ratatui_ruby-0.5.0.gem
 sources:
   - https://git.sr.ht/~kerrick/ratatui_ruby
 tasks:
@@ -24,8 +24,10 @@ tasks:
       curl https://mise.jdx.dev/install.sh | sh
       echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.buildenv
       echo 'eval "$($HOME/.local/bin/mise activate bash)"' >> ~/.buildenv
+      echo 'export LANG="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export LC_ALL="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export BINDGEN_EXTRA_CLANG_ARGS="-include stdbool.h"' >> ~/.buildenv
       . ~/.buildenv
-      export RUSTFLAGS="-C target-feature=-crt-static"
       export CI="true"
       cd ratatui_ruby
       sed -i 's/ruby = .*/ruby = "3.2"/' mise.toml

data/.builds/ruby-3.3.yml

@@ -1,22 +1,22 @@
 # SPDX-FileCopyrightText: 2025 Kerrick Long <me@kerricklong.com>
 # SPDX-License-Identifier: AGPL-3.0-or-later
 
-image: alpine/edge
+image: archlinux
 packages:
   - bash
-  - build-base
+  - base-devel
   - curl
-  - openssl-dev
-  - yaml-dev
-  - zlib-dev
-  - readline-dev
-  - gdbm-dev
-  - ncurses-dev
-  - libffi-dev
-  - clang-dev
+  - openssl
+  - libyaml
+  - zlib
+  - readline
+  - gdbm
+  - ncurses
+  - libffi
+  - clang
   - git
 artifacts:
-  - ratatui_ruby/pkg/ratatui_ruby-0.3.1.gem
+  - ratatui_ruby/pkg/ratatui_ruby-0.5.0.gem
 sources:
   - https://git.sr.ht/~kerrick/ratatui_ruby
 tasks:
@@ -24,8 +24,10 @@ tasks:
       curl https://mise.jdx.dev/install.sh | sh
       echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.buildenv
       echo 'eval "$($HOME/.local/bin/mise activate bash)"' >> ~/.buildenv
+      echo 'export LANG="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export LC_ALL="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export BINDGEN_EXTRA_CLANG_ARGS="-include stdbool.h"' >> ~/.buildenv
       . ~/.buildenv
-      export RUSTFLAGS="-C target-feature=-crt-static"
       export CI="true"
       cd ratatui_ruby
       sed -i 's/ruby = .*/ruby = "3.3"/' mise.toml

data/.builds/ruby-3.4.yml

@@ -1,22 +1,22 @@
 # SPDX-FileCopyrightText: 2025 Kerrick Long <me@kerricklong.com>
 # SPDX-License-Identifier: AGPL-3.0-or-later
 
-image: alpine/edge
+image: archlinux
 packages:
   - bash
-  - build-base
+  - base-devel
   - curl
-  - openssl-dev
-  - yaml-dev
-  - zlib-dev
-  - readline-dev
-  - gdbm-dev
-  - ncurses-dev
-  - libffi-dev
-  - clang-dev
+  - openssl
+  - libyaml
+  - zlib
+  - readline
+  - gdbm
+  - ncurses
+  - libffi
+  - clang
   - git
 artifacts:
-  - ratatui_ruby/pkg/ratatui_ruby-0.3.1.gem
+  - ratatui_ruby/pkg/ratatui_ruby-0.5.0.gem
 sources:
   - https://git.sr.ht/~kerrick/ratatui_ruby
 tasks:
@@ -24,8 +24,10 @@ tasks:
       curl https://mise.jdx.dev/install.sh | sh
       echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.buildenv
       echo 'eval "$($HOME/.local/bin/mise activate bash)"' >> ~/.buildenv
+      echo 'export LANG="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export LC_ALL="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export BINDGEN_EXTRA_CLANG_ARGS="-include stdbool.h"' >> ~/.buildenv
       . ~/.buildenv
-      export RUSTFLAGS="-C target-feature=-crt-static"
       export CI="true"
       cd ratatui_ruby
       sed -i 's/ruby = .*/ruby = "3.4"/' mise.toml

data/.builds/ruby-4.0.0.yml

@@ -1,22 +1,22 @@
 # SPDX-FileCopyrightText: 2025 Kerrick Long <me@kerricklong.com>
 # SPDX-License-Identifier: AGPL-3.0-or-later
 
-image: alpine/edge
+image: archlinux
 packages:
   - bash
-  - build-base
+  - base-devel
   - curl
-  - openssl-dev
-  - yaml-dev
-  - zlib-dev
-  - readline-dev
-  - gdbm-dev
-  - ncurses-dev
-  - libffi-dev
-  - clang-dev
+  - openssl
+  - libyaml
+  - zlib
+  - readline
+  - gdbm
+  - ncurses
+  - libffi
+  - clang
   - git
 artifacts:
-  - ratatui_ruby/pkg/ratatui_ruby-0.3.1.gem
+  - ratatui_ruby/pkg/ratatui_ruby-0.5.0.gem
 sources:
   - https://git.sr.ht/~kerrick/ratatui_ruby
 tasks:
@@ -24,8 +24,10 @@ tasks:
       curl https://mise.jdx.dev/install.sh | sh
       echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.buildenv
       echo 'eval "$($HOME/.local/bin/mise activate bash)"' >> ~/.buildenv
+      echo 'export LANG="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export LC_ALL="en_US.UTF-8"' >> ~/.buildenv
+      echo 'export BINDGEN_EXTRA_CLANG_ARGS="-include stdbool.h"' >> ~/.buildenv
       . ~/.buildenv
-      export RUSTFLAGS="-C target-feature=-crt-static"
       export CI="true"
       cd ratatui_ruby
       sed -i 's/ruby = .*/ruby = "4.0.0"/' mise.toml

data/AGENTS.md

@@ -13,162 +13,119 @@ Description: A high-performance Ruby wrapper for the Ratatui TUI library.
 
 Architecture:
 
--   **Frontend (Ruby):** Pure `Data` objects (Ruby 3.2+) defining the View Tree. Immediate mode.
--   **Backend (Rust):** A generic renderer using `ratatui` and `magnus` that traverses the Ruby `Data` tree and renders to the terminal buffer.
+- **Frontend (Ruby):** Pure `Data` objects (Ruby 3.2+) used in Frames and/or defining the View Tree. Immediate mode.
+- **Backend (Rust):** A generic renderer using `ratatui` and `magnus` that traverses the Ruby `Data` tree and renders to the terminal buffer.
 
-## 1. File & Coding Standards
+## Stability & Compatibility
 
-### Licensing & Copyright (Strict)
+- **Project Status:** Pre-1.0. 
+- **User Base:** 0 users (internal/experimental).
+- **Breaking Changes:** Backward compatibility is **NOT** a priority at this stage. Since there are no external users, you are encouraged to refactor APIs for better ergonomics and performance even if it breaks existing code.
+- **Requirement:** All breaking changes **MUST** be explicitly documented in the [CHANGELOG.md](CHANGELOG.md)'s **Unreleased** section to ensure transparency as the project evolves toward 1.0.
 
-Every file must begin with an SPDX-compliant header. Use the following format:
+## 1. Standards
 
-```ruby
-# frozen_string_literal: true
+### STRICT REQUIREMENTS
 
-# SPDX-FileCopyrightText: 2025 Kerrick Long <me@kerricklong.com>
-# SPDX-License-Identifier: AGPL-3.0-or-later
-```
+- Every file MUST begin with an SPDX-compliant header. Use `AGPL-3.0-or-later` for code; `CC-BY-SA-4.0` for documentation. `reuse annotate` can help you generate the header.
+- Every line of Ruby MUST be covered by tests that would stand up to mutation testing.
+  - Tests must be meaningful and verify specific behavior or rendering output; simply verifying that code "doesn't crash" is insufficient and unacceptable.
+  - For UI widgets, this means using `with_test_terminal` to verify EVERY character of the terminal buffer's content.
+- Every line of Rust MUST be covered by tests that would stand up to mutation testing.
+  - Tests must be meaningful; simply verifying that code "doesn't crash" or "compiles" is insufficient and unacceptable.
+  - Each widget implementation must have a `tests` module with unit tests verifying basic rendering.
+- **Pre-commit:** Use `bin/agent_rake` to ensure commit-readiness. See Tools for detailed instructions.
+- **Git Pager:** ALWAYS set `PAGER=cat` for ALL `git` commands (e.g., `PAGER=cat git diff`). This is mandatory.
 
--   **Ruby/Rust/Config files:** Use comments appropriate for the language (`#` or `//`).
--   **Markdown:** Use HTML comment style `<!-- -->`.
--   **Exceptions:** `REUSE.toml` manages exceptions (e.g., binary files or `.gitignore`).
+### Tools
+
+- **NEVER** run `bundle exec rake` directly. **NEVER** run `bundle exec ruby -Ilib:test ...` directly.
+- **ALWAYS use `bin/agent_rake`** for running tests, linting, or checking compilation.
+  - **Usage:**
+    - Runs default task (compile + test + lint): `bin/agent_rake`
+    - Runs specific task: `bin/agent_rake test:ruby` (for example)
+- **Setup:** `bin/setup` must handle both Bundler and Cargo dependencies.
+- **Git:** ALWAYS set `PAGER=cat` with `git`, `git`, etc.. **THIS IS CRITICAL!**
+- **Rake:** Our rake tasks use `git ls-files`, so errors happen when you move or delete files. In this case, ask the user to stage changes for you.
 
 ### Ruby Standards
 
--   **Version:** Tested against the latest releases of Ruby 3.2, 3.3, 3.4, and 4.0, and must work on all of them. Local development happens on the latest stable release.
--   **Linter:** Run via `bundle exec rake lint`. You are not done until all linting passes.
--   **Style:**
-    -   Use `Data.define` for all value objects (UI Nodes). (Prefer `class Foo < Data.define()` over `Foo = Data.define() do`).
-    -   Prefer `frozen_string_literal: true`.
-    -   Use `Minitest` for testing.
-    -   Define types in `.rbs` files. Don't use `untyped` just because it's easy; be comprehensive and accurate. Do not include `initialize` in `.rbs` files; use `self.new` for constructors instead.
-    -   Every line of Ruby must be covered by tests that would stand up to mutation testing. This includes all examples in the `examples/` directory; they should have corresponding tests in `examples/` to ensure they continue to work as intended and serve as reliable documentation. Tests must be meaningful and verify specific behavior or rendering output; simply verifying that code "doesn't crash" is insufficient and unacceptable. For UI widgets, this means using `with_test_terminal` to verify every character of the terminal buffer's content.
-    -   Every public Ruby class/method must be documented for humans in RDoc (preferred)--**not** YARD--or markdown files (fallback), and must have `*.rbs` types defined.
-    -   Every significant architectural and design decision must be documented for contributors in markdown files. Mermaid is allowed.
+- Use `Data.define` for all value objects (UI Nodes). (Prefer `class Foo < Data.define()` over `Foo = Data.define() do`).
+- Define types in `.rbs` files. Don't use `untyped` just because it's easy; be comprehensive and accurate. Do not include `initialize` in `.rbs` files; use `self.new` for constructors instead.
+- Every public Ruby class/method must be documented for humans in RDoc (preferred)--**not** YARD--or markdown files (fallback), and must have `*.rbs` types defined.
+- Every significant architectural and design decision must be documented for contributors in markdown files. Mermaid is allowed.
+- **Rust-backed methods:** For methods implemented in Rust (magnus bindings), use RDoc directives instead of empty method bodies. Use `##` followed by `:method:`, `:call-seq:`, and prose. End with `(Native method implemented in Rust)`. See `lib/ratatui_ruby.rb` for examples.
+- Refer to [docs/contributors/design/ruby_frontend.md](docs/contributors/design/ruby_frontend.md) for detailed design philosophy regarding the Immediate Mode paradigm including Data-Driven UI and Frames.
 
 ### Rust Standards
 
--   **Crate Type:** `cdylib`.
--   **Linter:** `clippy` and `rustfmt`.
--   **Bindings:** Use [magnus](https://github.com/matsadler/magnus).
--   **Platform:** Support macOS (Apple Silicon), Linux, and Windows.
--   **Linker Flags:** Must handle macOS `-undefined dynamic_lookup`.
--   Every line of Rust must be covered by tests that would stand up to mutation testing. This includes every widget implementation in `ext/ratatui_ruby/src/widgets/`; each must have a `tests` module with unit tests verifying basic rendering. Tests must be meaningful; simply verifying that code "doesn't crash" or "compiles" is insufficient.
+- **Crate Type:** `cdylib`.
+- **Bindings:** Use [magnus](https://github.com/matsadler/magnus).
+- **Platform:** Support macOS (Apple Silicon), Linux, and Windows.
+- Refer to [docs/contributors/design/rust_backend.md](docs/contributors/design/rust_backend.md) for detailed implementation guidelines, module structure, and rendering logic.
 
 ## 2. Directory Structure Convention
 
-The project follows a standard Gem layout with an `ext/` directory for Rust code.
-
-```plaintext
-/
-├── .cargo/                 # Cargo configuration (linker flags)
-├── .github/                # CI/CD workflows
-├── bin/                    # Executables (console, setup)
-├── docs/                   # Documentation tree
-│   ├── contributors/       # Design docs, ecosystem notes
-│   └── index.md
-├── ext/
-│   └── ratatui_ruby/       # RUST SOURCE CODE GOES HERE
-│       ├── src/
-│       │   └── lib.rs      # Entry point
-│       ├── Cargo.toml
-│       └── extconf.rb      # Makefile generator
-├── lib/
-│   ├── ratatui_ruby/
-│   │   ├── schema/         # Ruby Data definitions
-│   │   └── version.rb
-│   └── ratatui_ruby.rb     # Main loader
-├── test/
-│   ├── data/               # Data-driven test files
-│   └── ratatui_ruby/       # Unit tests
-├── vendor/                 # Vendorized style configs (goodcop)
-├── AGENTS.md               # Context for AI agents
-├── Gemfile
-├── Rakefile
-├── REUSE.toml              # Compliance definition
-└── ratatui_ruby.gemspec
-```
+The project follows a standard Gem layout with an `ext/` directory for Rust code and `examples/` for example application-level code.
 
 ## 3. Configuration & Tooling
 
 ### Development Environment
 
--   **Setup:** `bin/setup` must handle both Bundler and Cargo dependencies.
--   **Pre-commit:** Use `.pre-commit-config.yaml` to enforce `bundle exec rake` and `cargo fmt`.
 
 ### Documentation
 
--   Follow the `docs/` structure: `index.md` -> `contributors/` | `quickstart.md`.
--   Documentation should separate "User Guide" (Ruby API for TUI developers) from "Contributor Guide" (Ruby/Rust/Magnus internals).
--   Don't write .md files for something RDoc (Ruby) or rustdoc (Rust) can generate.
--   **The `doc/` folder contains source markdown files** that are included in RDoc output. You can edit these files.
--   **The `tmp/rdoc/` folder is auto-generated** by `bundle exec rake rerdoc`. Never edit files in `tmp/rdoc/` directly.
-
-## 4. The Ruby <-> Rust Bridge Contract
-
-### The Ruby Side (`lib/`)
-
--   Refer to [docs/contributors/design/ruby_frontend.md](docs/contributors/design/ruby_frontend.md) for detailed design philosophy regarding the Data-Driven UI and Immediate Mode paradigm.
-
-### The Rust Side (`ext/`)
-
--   Refer to [docs/contributors/design/rust_backend.md](docs/contributors/design/rust_backend.md) for detailed implementation guidelines, module structure, and rendering logic.
-
-## 5. Deployment / Release
-
--   The gem builds a native extension.
--   Artifact naming: Ensure the output shared library matches Ruby's expectation on macOS (rename `.dylib`to `.bundle` if necessary during the build process in `extconf.rb` or `Rakefile`).
-
-## 6. Source Control Standards
-
--   **Commits:**
-    -   Who commits: Only humans should affect the git index and history. Rather than staging and/or committing, you should suggest a commit message.
-    -   When: At the end of each task, before reporting the task as complete to the user, suggest the commit message.
--   **Format:**
-    -   Subject line: Concise summary (50 chars or less).
-    -   Body: Detailed explanation if necessary (wrap at 72 chars). Explain why this is the implementation, as opposed to other possible implementations. Skip the body entirely if it's rote, a duplication of the diff, or otherwise unhelpful. **Do not simply list the files changed or the minor edits made to them.** Do not use markdown, except as required in AI Attribution.
-    -   Footer: AI attribution if generated by an agent, sourcehut ticket if implemented by a ticket, or both.
--   **AI Attribution:**
-     -   **Always include AI attribution** in the footer if the commit was generated or significantly assisted by an AI agent. This is mandatory for transparency and compliance.
-     -   **Amp:**
-         ```
-         Generated with [Amp](https://ampcode.com)
-
-         Co-Authored-By: Amp <noreply@ampcode.com>
-         ```
-     -   **Antigravity:**
-         Specify the model used in the footer. Examples:
-         ```
-         Generated with [Antigravity](https://antigravity.google)
-
-         Co-Authored-By: Gemini 3 Pro (High) <noreply@google.com>
-         ```
-         ```
-         Generated with [Antigravity](https://antigravity.google)
-
-         Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
-         ```
-     -   **Gemini 3:**
-         ```
-         Generated with [Gemini 3 Pro](https://gemini.google.com/)
-
-         Co-Authored-By: Gemini 3 Pro <noreply@google.com>
-         ```
-     -   **JetBrains Junie:**
-         ```
-         Generated with [JetBrains Junie](https://www.jetbrains.com/ai/)
-
-         Co-Authored-By: Junie <junie@jetbrains.com>
-         ```
--   **Sourcehut Tickets:**
-    - If the commit implements a specific ticket, include a footer: `Implements: https://todo.sr.ht/~kerrick/ratatui_ruby/<id>`
-    - This must be the **last** item in the footer, if present.
-
-## 7. Definition of Done
+- **The `doc/` folder contains source markdown files** that are included in RDoc output.
+- Documentation should separate "User Guide" (Ruby API for TUI developers) from "Contributor Guide" (Ruby/Rust/Magnus internals).
+  - Files within `doc/contributors/` are for library developers.
+  - Files within `doc/` outside of `conttributors/` are for application developers and users of this RubyGEm.
+- **Style Guide:** You **MUST** follow the [Documentation Style Guide](doc/contributors/documentation_style.md). This dictates the Alexandrian/Zinsser prose style and strict RDoc formatting required for all public API documentation.
+- DON'T write .md files for something RDoc (Ruby) or rustdoc (Rust) can generate. DO use RDoc and rustdoc for documentation.
+
+
+## 4. Committing
+
+- Who commits: DON'T stage (DON'T `git add`). DON'T commit. DO suggest a commit message.
+- When: Before reporting the task as complete to the user, suggest the commit message.
+- What: Consider not what you remember, but EVERYTHING in the `git diff` and `git diff --cached`.
+- **Format:**
+    - Format: Use [Conventional Commits](https://www.conventionalcommits.org/).
+    - Body: Explanation if necessary (wrap at 72 chars).
+        - Explain why this is the implementation, as opposed to other possible implementations.
+        - Skip the body entirely if it's rote, a duplication of the diff, or otherwise unhelpful.
+        - **DON'T list the files changed or the edits made in the body.** Don't provide a bulleted list of changes. Use prose to explain the problem and the solution.
+        - **DON'T use markdown syntax** (no backticks, no bolding, no lists, no links). The commit message must be plain text.
+  
+### 5. Changelog
+
+- Follow [Semantic Versioning](https://semver.org/)
+- Follow the [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) specification.
+- **What belongs in CHANGELOG:** Only changes that affect **application developers** or **higher-level library developers** who use or depend on `ratatui_ruby`:
+    - New public APIs or widget parameters
+    - Backwards-incompatible type signature changes, or behavioral additions to type signature changes
+    - Observable behavior changes (rendering, styling, layout)
+    - Deprecations and removals
+    - Breaking changes
+- **What does NOT belong in CHANGELOG:** Internal or non-behavioral changes that don't affect downstream users:
+    - Test additions or improvements
+    - Documentation updates, RDoc fixes, markdown clarifications
+    - Refactors of internal code
+    - New or modified example code
+    - Internal tooling, CI/CD, or build configuration changes
+    - Code style or linting changes
+    - Performance improvements that affect applications
+- Changelogs should be useful to downstream developers (both app and library developers), not simple restatements of diffs or commit messages.
+- The Unreleased section MUST be considered "since the last git tag". Therefore, if a change was done in one commit and undone in another (both since the last tag), the second commit should remove its changelog entry.
+- **Location:** New entries ALWAYS go in `## [Unreleased]`. Never edit past version sections (e.g., `## [0.4.0]`)—those are frozen history.
+
+## 6. Definition of Done (DoD)
 
 Before considering a task complete and returning control to the user, you **MUST** ensure:
 
-1.  **Tests & Linting Pass:** Run `bundle exec rake` and confirm it passes. No new errors **or warnings** should be introduced.
-2.  **Documentation Updated:** If public APIs or observable behavior changed, update relevant `doc/` files, `README.md`, and/or `ratatui_ruby-wiki` files,.
-3.  **Changelog Updated:** If public APIs, observable behavior, or gemspec dependencies changed, update [CHANGELOG.md](CHANGELOG.md)'s **Unreleased** section according to the [Semantic Versioning](https://semver.org/) and [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) specifications. Changelogs should be useful to human users of the library, not simple restatements of diffs or commit messages. **Do not add entries for internal tooling, CI, or build configuration changes that do not affect the distributed gem.**
+1.  **Default Rake Task Passes:** Run `bin/agent_rake` (no args). Confirm it passes with ZERO errors **or warnings**.
+  - You will save time if you run `bin/agent_rake rubocop:autocorrect` first.
+  - If you think the build is looking for deleted files, it is not. Instead, tell the user and **ask them to stage changes**.
+2.  **Documentation Updated:** If public APIs or observable behavior changed, update relevant RDoc, rustdoc, `doc/` files, `README.md`, and/or `ratatui_ruby-wiki` files.
+3.  **Changelog Updated:** If public APIs, observable behavior, or gemspec dependencies have changed, update [CHANGELOG.md](CHANGELOG.md)'s **Unreleased** section.
 4.  **Commit Message Suggested:** You **MUST** ensure the final message to the user includes a suggested commit message block. This is NOT optional.
+  - You MUST also remind the user to add an AI attribution footer.