feat(otty): adopt a widgets-first workspace architecture

Author: Harzu

.github/workflows/lint.yaml

@@ -15,5 +15,6 @@ jobs:
     steps:
     - uses: actions/checkout@v3
     - uses: dtolnay/rust-toolchain@stable
-    - run: cargo fmt --all -- --check
+    - run: cargo +nightly fmt --all -- --check
     - run: cargo lint
+    - run: cargo test -p otty --test widget_conventions_ast --locked --all-features

.github/workflows/tests.yaml

@@ -20,4 +20,5 @@ jobs:
       - uses: Swatinem/rust-cache@v2
         with:
           save-if: ${{ github.ref == 'refs/heads/main' }}
+      - run: cargo test -p otty --test widget_conventions_ast --locked --all-features --verbose
       - run: cargo test --locked --all-features --verbose

AGENTS.md

@@ -1,22 +1,24 @@
 # AGENTS Instructions
 
-General context lives in `README.md` at the repository root.
+General context lives in [README.md](./README.md) at the repository root.
 
 ## Development workflow
 
 - Crate names stay prefixed with `otty-`.
 - Prefer `format!("{value}")`-style interpolation instead of passing variables as separate arguments when formatting strings.
-- When touching Rust code, run `cargo fmt` followed by `cargo clippy --workspace --all-targets`. Fix warnings wherever practical.
-- Run `cargo test -p <crate>` (or `cargo test --workspace`) before submitting changes that affect logic-heavy crates like `otty-escape` or `otty-pty`.
 - Add concise documentation comments to new public items to communicate intent.
 - Prefer borrowing over cloning; pass `&T`/`&str` where possible and keep ownership at boundaries.
 - Avoid unnecessary heap allocations; use slices and references for read-only data.
 - Use `Result`/`Option` for error handling; no `unwrap()` in production code (prefer `expect()` with context during initialization).
 - Use explicit error types (e.g., with `thiserror`) and propagate with `?`.
 - Keep APIs minimal and trait-based; use associated types for event/action contracts.
-- Prefer `format!("{value}")` style interpolation for strings.
+- Do not expose struct fields as `pub`; use idiomatic Rust accessors for reads (`field()` or `is_*` for booleans), and prefer domain-specific mutators for writes (use `set_*` only when a generic setter is the clearest option, or keep mutation local to the module). Exception: plain input/context structs with no invariants to protect (e.g. feature `Ctx` types passed into `reduce`) MAY use `pub(crate)` fields directly — accessors would be unnecessary boilerplate for parameter bags.
+- For `match` on `enum`, prefer a wildcard arm (`_ => ...`) by default for fallback logic.
 - Document public items with concise doc comments and examples.
-- Run `cargo fmt`, `cargo clippy --workspace --all-targets`, and relevant `cargo test` targets after changes.
+- Run `cargo +nightly fmt`, `cargo clippy --workspace --all-targets --all-features -- -D warnings` and fix all errors and warnings.
+- Run `cargo deny check` and fix all output errors.
+- Run `cargo test --workspace --all-features` all tests MUST be passed
+- Run `cargo llvm-cov --workspace --all-features --fail-under-lines 80` for checking the test coverage level and ensure that it's not decreased for changed code (baseline >= 80%)
 
 ## Terminal emulation
 

CLAUDE.md

@@ -0,0 +1 @@
+@AGENTS.md