@tayo-dev/rtl 1.3.1 → 1.4.0

package/README.md

@@ -1,8 +1,8 @@
-# Taro
+# Tayo
 
-Install Taro into Claude Code, OpenCode, Gemini CLI, or Codex, then generate React Testing Library tests from Testing Library Recorder recordings.
+Install Tayo into Claude Code, OpenCode, Gemini CLI, or Codex, then generate React Testing Library tests from Testing Library Recorder recordings.
 
-Taro ships as an installer-first package. The package entrypoint bootstraps runtime-native commands or skills into your agent environment, and the generated runtime surface still routes back to `taro generate` when you want Recorder-to-RTL output.
+Tayo ships as an installer-first package. The package entrypoint bootstraps runtime-native commands or skills into your agent environment, and the generated runtime surface still routes back to `tayo generate` when you want Recorder-to-RTL output.
 
 ## Getting Started
 
@@ -33,7 +33,7 @@ Re-run the installer package to refresh owned assets and repair missing ones:
 npx @tayo-dev/rtl@latest
 ```
 
-Taro refreshes unchanged owned files automatically, restores missing owned files, and protects manual edits instead of overwriting them silently.
+Tayo refreshes unchanged owned files automatically, restores missing owned files, and protects manual edits instead of overwriting them silently.
 
 ## Non-interactive Install
 
@@ -80,15 +80,15 @@ npm run build
 node dist/index.js --all --local
 
 # Or verify the publish boundary with a tarball
-env NPM_CONFIG_CACHE=/tmp/taro-npm-cache npm pack --pack-destination /tmp/taro-pack
-npx /tmp/taro-pack/tayo-dev-rtl-1.0.0.tgz --codex --local
+env NPM_CONFIG_CACHE=/tmp/tayo-npm-cache npm pack --pack-destination /tmp/tayo-pack
+npx /tmp/tayo-pack/tayo-dev-rtl-1.0.0.tgz --codex --local
 ```
 
 The tarball flow is the closest match to what end users get from npm.
 
 ## Generate RTL Tests
 
-After installation, use `taro generate` directly or call the runtime-native installed command/skill that routes to it.
+After installation, use `tayo generate` directly or call the runtime-native installed command/skill that routes to it.
 
 ### Prerequisites
 
@@ -100,7 +100,7 @@ After installation, use `taro generate` directly or call the runtime-native inst
 
 Open Chrome DevTools → Recorder panel → click "Start new recording" → perform your user flow → click "End recording".
 
-Taro supports two export paths:
+Tayo supports two export paths:
 
 - Testing Library Recorder JS baseline export: save as `recording.js`
 - Chrome Recorder JSON export: save as `recording.json`
@@ -109,39 +109,39 @@ Taro supports two export paths:
 
 ```bash
 # JS baseline path
-taro generate ./recording.js
+tayo generate ./recording.js
 
 # Supported JSON path
-taro generate ./recording.json
+tayo generate ./recording.json
 ```
 
 Expected output:
 
 ```text
 Parsed: my user flow — 8 steps
-[taro] Score: 78/100 (B) — query: 80, assertions: 70, structure: 85
+[tayo] Score: 78/100 (B) — query: 80, assertions: 70, structure: 85
 Created: src/components/MyComponent.test.tsx
-[taro] ✓ post-write verified
+[tayo] ✓ post-write verified
 ```
 
-On subsequent runs in the same project, Taro reads `.taro/conventions.json` to match your test style automatically.
+On subsequent runs in the same project, Tayo reads `.tayo/conventions.json` to match your test style automatically.
 
 ### Draft-quality output is explicit
 
-When Taro cannot prove the final render/query boundary yet, it keeps the output writable but marks it as draft-quality instead of pretending the gaps are solved.
+When Tayo cannot prove the final render/query boundary yet, it keeps the output writable but marks it as draft-quality instead of pretending the gaps are solved.
 
 ```text
-[taro] Score: 77/100 (C) — query: 100, assertions: 30, structure: 70, boundary: 100
-[taro] Manual review required — this generated test is still a draft (77/100, C).
-[taro] Top blockers: The generated test still renders <App /> instead of a resolved repo target. | Boundary warnings remain in the generated file, so the render/mock boundary still needs cleanup.
-// taro-query-checkpoint: click step requires manual RTL query recovery
+[tayo] Score: 77/100 (C) — query: 100, assertions: 30, structure: 70, boundary: 100
+[tayo] Manual review required — this generated test is still a draft (77/100, C).
+[tayo] Top blockers: The generated test still renders <App /> instead of a resolved repo target. | Boundary warnings remain in the generated file, so the render/mock boundary still needs cleanup.
+// tayo-query-checkpoint: click step requires manual RTL query recovery
 ```
 
-That draft banner is advisory. Taro does not block writes, but it does tell you when import targets, placeholder queries, or unresolved boundaries still need cleanup.
+That draft banner is advisory. Tayo does not block writes, but it does tell you when import targets, placeholder queries, or unresolved boundaries still need cleanup.
 
 ## CLI Reference
 
-### `taro generate <file>`
+### `tayo generate <file>`
 
 Generates a React Testing Library test from a Testing Library Recorder JS export or a Chrome Recorder JSON export.
 
@@ -157,7 +157,7 @@ Generates a React Testing Library test from a Testing Library Recorder JS export
 |------|-------|---------|-------------|
 | `--output <path>` | `-o` | Same directory as input, `{name}.test.tsx` | Override the output file path for the generated test. |
 | `--dry-run` | `-d` | `false` | Print the generated test to stdout and show the score without writing to disk. Useful for previewing output before committing. |
-| `--force` | `-f` | `false` | Overwrite an existing test file. Without this flag, Taro exits with an error if the output file already exists. |
+| `--force` | `-f` | `false` | Overwrite an existing test file. Without this flag, Tayo exits with an error if the output file already exists. |
 | `--version` | `-v` | — | Print the installed version and exit. |
 | `--help` | `-h` | — | Display command help and exit. |
 
@@ -165,24 +165,24 @@ Generates a React Testing Library test from a Testing Library Recorder JS export
 
 ```bash
 # Generate and write a test next to the recording
-taro generate ./recordings/checkout-flow.js
+tayo generate ./recordings/checkout-flow.js
 
 # Preview without writing (dry run)
-taro generate --dry-run ./recordings/checkout-flow.js
+tayo generate --dry-run ./recordings/checkout-flow.js
 
 # Write to a specific path
-taro generate --output src/__tests__/checkout.test.tsx ./recordings/checkout-flow.js
+tayo generate --output src/__tests__/checkout.test.tsx ./recordings/checkout-flow.js
 
 # Overwrite an existing test
-taro generate --force ./recordings/checkout-flow.js
+tayo generate --force ./recordings/checkout-flow.js
 ```
 
 **Output file naming:**
-If `--output` is not provided, Taro derives the output path from the input file: `{input-dir}/{input-basename}.test.tsx`. For example, `./recordings/login.js` → `./recordings/login.test.tsx`.
+If `--output` is not provided, Tayo derives the output path from the input file: `{input-dir}/{input-basename}.test.tsx`. For example, `./recordings/login.js` → `./recordings/login.test.tsx`.
 
 **Supported input formats:**
-- Testing Library Recorder JS (`.js`) — primary v1.3 path; Taro treats this as a baseline artifact to parse, enrich, and transform into a project-shaped RTL test
-- Chrome Recorder JSON (`.json`) — supported parity path; Taro preserves the existing JSON generate flow while JS fidelity improves
+- Testing Library Recorder JS (`.js`) — primary v1.3 path; Tayo treats this as a baseline artifact to parse, enrich, and transform into a project-shaped RTL test
+- Chrome Recorder JSON (`.json`) — supported parity path; Tayo preserves the existing JSON generate flow while JS fidelity improves
 
 ## Worked Example
 
@@ -207,21 +207,21 @@ test('login flow', async () => {
 ### Command
 
 ```bash
-taro generate ./login-flow.js
+tayo generate ./login-flow.js
 ```
 
 ### Terminal output
 
 ```
 Parsed: login flow — 7 steps
-[taro] Score: 82/100 (B) — query: 90, assertions: 75, structure: 80
+[tayo] Score: 82/100 (B) — query: 90, assertions: 75, structure: 80
 Created: login-flow.test.tsx
-[taro] ✓ post-write verified
+[tayo] ✓ post-write verified
 ```
 
 ### Output: Generated test (`login-flow.test.tsx`)
 
-Taro generates a convention-aware RTL test with accessible queries:
+Tayo generates a convention-aware RTL test with accessible queries:
 
 ```typescript
 import { render, screen } from '@testing-library/react'
@@ -244,7 +244,7 @@ describe('login flow', () => {
 })
 ```
 
-### What Taro did here
+### What Tayo did here
 
 - Parsed the navigate step and inferred the component under test
 - Upgraded CSS selectors (`#email`, `#password`) to accessible `getByRole` queries using aria attributes from the recording
@@ -252,30 +252,30 @@ describe('login flow', () => {
 - Mapped the `waitForElement` step to a `toBeInTheDocument()` assertion
 - Scored the output (82/100) and emitted no blocking errors
 
-> **Note:** The component import path (`../LoginPage`) is a placeholder. Taro generates a comment in the file indicating where to update it.
+> **Note:** The component import path (`../LoginPage`) is a placeholder. Tayo generates a comment in the file indicating where to update it.
 
 ### JSON is also supported
 
 If you export Chrome Recorder JSON instead, the command surface stays the same:
 
 ```bash
-taro generate ./login-flow.json --dry-run
+tayo generate ./login-flow.json --dry-run
 ```
 
-JSON generation is still supported, but it does not inherit the repo-aware JS recovery stack. When the generated preview contains placeholder queries or weak assertions, Taro keeps those gaps explicit with score and manual-review messaging instead of fabricating stronger evidence.
+JSON generation is still supported, but it does not inherit the repo-aware JS recovery stack. When the generated preview contains placeholder queries or weak assertions, Tayo keeps those gaps explicit with score and manual-review messaging instead of fabricating stronger evidence.
 
 ## Agent Usage
 
-After installation, each runtime gets a namespaced help entrypoint plus a generate command or skill that routes back to `taro generate`.
+After installation, each runtime gets a namespaced help entrypoint plus a generate command or skill that routes back to `tayo generate`.
 
 ### Tips
 
 - Use `--dry-run` first to preview output before committing generated files
-- If you record multiple flows, run Taro on each to build up convention state in `.taro/conventions.json` — later runs benefit from earlier ones
+- If you record multiple flows, run Tayo on each to build up convention state in `.tayo/conventions.json` — later runs benefit from earlier ones
 - Pass `--force` when re-recording an updated flow to overwrite the old test
-- The `.taro/` directory should be committed to your repo so convention learning persists across team members
+- The `.tayo/` directory should be committed to your repo so convention learning persists across team members
 
 ### Notes
 
-- Taro does not require network access at generation time (DOM inspection via Playwright is optional and only runs when a live URL is in the recording)
-- All state is local to `.taro/` — no external service is contacted
+- Tayo does not require network access at generation time (DOM inspection via Playwright is optional and only runs when a live URL is in the recording)
+- All state is local to `.tayo/` — no external service is contacted

package/assets/claude/commands/@tayo-dev/rtl/generate.md

@@ -1,6 +1,6 @@
 ---
 name: "@tayo-dev/rtl:generate"
-description: "Generate RTL tests from Recorder exports with Taro"
+description: "Generate RTL tests from Recorder exports with Tayo"
 ---
 
 <objective>
@@ -9,7 +9,7 @@ Generate a React Testing Library test from a Recorder export.
 
 <process>
 1. Confirm the recording path before running anything destructive.
-2. Run `taro generate <recording-file>` by default.
+2. Run `tayo generate <recording-file>` by default.
 3. Add `--dry-run`, `--output <path>`, or `--force` only when the user asks for them or the context requires them.
 4. Report the generated file path and score output.
 </process>

package/assets/claude/commands/@tayo-dev/rtl/help.md

@@ -10,7 +10,7 @@ Help the user install and use @tayo-dev/rtl from Claude Code.
 <process>
 1. Explain that `/@tayo-dev/rtl:help` is the installed help entrypoint for @tayo-dev/rtl.
 2. For installation or updates, tell the user to run `npx @tayo-dev/rtl@latest`.
-3. For test generation, use `/@tayo-dev/rtl:generate` or run `taro generate <recording-file>`.
+3. For test generation, use `/@tayo-dev/rtl:generate` or run `tayo generate <recording-file>`.
 4. Mention `--dry-run`, `--output <path>`, and `--force` only when they fit the request.
 5. When generation runs, report the score and generated file path.
 </process>

package/assets/codex/@tayo-dev/rtl-conventions/SKILL.md

@@ -5,12 +5,12 @@ description: "Explain how Tayo learns project test conventions and how to keep t
 
 # Tayo Conventions
 
-Use `$@tayo-dev/rtl-conventions` when the user asks why generated tests follow a certain style or how `.taro/conventions.json` affects output.
+Use `$@tayo-dev/rtl-conventions` when the user asks why generated tests follow a certain style or how `.tayo/conventions.json` affects output.
 
 ## Focus
 
 - explain that Tayo learns local test conventions from the codebase
-- call out when `.taro/conventions.json` will influence generated imports, mocks, and file placement
+- call out when `.tayo/conventions.json` will influence generated imports, mocks, and file placement
 - recommend `--dry-run` when the user wants to inspect convention alignment before writing files
 
 ## Guardrails

package/assets/codex/@tayo-dev/rtl-generate/SKILL.md

@@ -16,7 +16,7 @@ Use `$@tayo-dev/rtl-generate` when the user wants to turn a Recorder JS export o
 
 ## Execution
 
-Run `taro generate <recording-file>` with the requested flags.
+Run `tayo generate <recording-file>` with the requested flags.
 
 ## Response contract
 

package/assets/codex/@tayo-dev/rtl-help/SKILL.md

@@ -21,5 +21,5 @@ Invoke this skill with `$@tayo-dev/rtl-help`.
 
 1. Confirm the recording path or test target.
 2. Choose the matching packaged Tayo skill.
-3. If direct CLI execution is appropriate, run `taro generate <recording-file>` with any requested flags.
+3. If direct CLI execution is appropriate, run `tayo generate <recording-file>` with any requested flags.
 4. Report the generated file path, score, and any blocking issues.

package/assets/gemini/commands/@tayo-dev/rtl/generate.toml

@@ -1,10 +1,10 @@
-description = "Generate RTL tests from Recorder exports with Taro"
+description = "Generate RTL tests from Recorder exports with Tayo"
 prompt = """
 You are the installed /@tayo-dev/rtl:generate command for @tayo-dev/rtl.
 
 Generate a React Testing Library test from a Recorder export.
 1. Confirm the recording path before running anything destructive.
-2. Run `taro generate <recording-file>` by default.
+2. Run `tayo generate <recording-file>` by default.
 3. Add `--dry-run`, `--output <path>`, or `--force` only when the user asks for them or the context requires them.
 4. Report the generated file path and score output.
 """

package/assets/gemini/commands/@tayo-dev/rtl/help.toml

@@ -5,7 +5,7 @@ You are the installed /@tayo-dev/rtl:help command for @tayo-dev/rtl.
 When the user wants help:
 1. Explain that /@tayo-dev/rtl:help is the runtime-native help entrypoint.
 2. For installation or updates, tell them to run `npx @tayo-dev/rtl@latest`.
-3. For generation, direct them to /@tayo-dev/rtl:generate or `taro generate <recording-file>`.
+3. For generation, direct them to /@tayo-dev/rtl:generate or `tayo generate <recording-file>`.
 4. Mention `--dry-run`, `--output <path>`, and `--force` only when they match the request.
 5. When generation runs, report the score and generated file path.
 """

package/assets/opencode/commands/@tayo-dev/rtl-generate.md

@@ -1,11 +1,11 @@
 ---
-description: Generate RTL tests from Recorder exports with Taro
+description: Generate RTL tests from Recorder exports with Tayo
 ---
 
 You are the installed `/@tayo-dev/rtl-generate` command for `@tayo-dev/rtl`.
 
 Generate a React Testing Library test from a Recorder export.
 1. Confirm the recording path before running anything destructive.
-2. Run `taro generate <recording-file>` by default.
+2. Run `tayo generate <recording-file>` by default.
 3. Add `--dry-run`, `--output <path>`, or `--force` only when the user asks for them or the context requires them.
 4. Report the generated file path and score output.

package/assets/opencode/commands/@tayo-dev/rtl-help.md

@@ -7,6 +7,6 @@ You are the installed `/@tayo-dev/rtl-help` command for `@tayo-dev/rtl`.
 When the user wants help:
 1. Explain that `/@tayo-dev/rtl-help` is the runtime-native help entrypoint.
 2. For installation or updates, tell them to run `npx @tayo-dev/rtl@latest`.
-3. For generation, direct them to `/@tayo-dev/rtl-generate` or `taro generate <recording-file>`.
+3. For generation, direct them to `/@tayo-dev/rtl-generate` or `tayo generate <recording-file>`.
 4. Mention `--dry-run`, `--output <path>`, and `--force` only when they match the request.
 5. When generation runs, report the score and generated file path.

package/dist/cli/commands/generate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"generate.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/generate.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAA;AA+CnC,MAAM,WAAW,eAAe;IAC9B,MAAM,CAAC,EAAE,MAAM,CAAA;IACf,MAAM,CAAC,EAAE,OAAO,CAAA;IAChB,KAAK,CAAC,EAAE,OAAO,CAAA;CAChB;AA2lBD,wBAAgB,qBAAqB,IAAI,OAAO,CAqL/C"}
+{"version":3,"file":"generate.d.ts","sourceRoot":"","sources":["../../../src/cli/commands/generate.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,OAAO,EAAE,MAAM,WAAW,CAAA;AAiDnC,MAAM,WAAW,eAAe;IAC9B,MAAM,CAAC,EAAE,MAAM,CAAA;IACf,MAAM,CAAC,EAAE,OAAO,CAAA;IAChB,KAAK,CAAC,EAAE,OAAO,CAAA;CAChB;AAo2BD,wBAAgB,qBAAqB,IAAI,OAAO,CAoN/C"}