Merge pull request #4930 from udecode/codex/4111-table-border-wrong-cell

Author: zbeyens

.agents/AGENTS.md

@@ -1,6 +1,8 @@
+- `.agents/AGENTS.md` and `.agents/rules/*.mdc` are source of truth. After editing them, run `bun install` to sync. Never edit `SKILL.md` directly.
 - In all interactions and commit messages, be extremely concise and sacrifice grammar for the sake of concision.
 - ALWAYS read and understand relevant files before proposing edits. Do not speculate about code you have not inspected.
-- Never browse GitHub, use `gh` instead. Use `dig` skill when the user asks a question about a library, needs to understand a library's API, or when you need information about a library that you don't know about.
+- Never browse GitHub files. For library/API questions or unfamiliar deps, inspect the repo at `..`; if missing, clone `https://github.com/{owner}/{repo}.git` to `../{repo-name}`.
+- For repo research, use `spawn_agent(... agent_type=\"explorer\")` and return file-backed findings from docs, structure, exports, examples, and tests only.
 - Dirty workspace: Never pause to ask about unrelated local changes. Continue work and ignore unrelated diffs.
 - Proactively use Skill(tdd) when it adds value; skip TDD for high-friction tests like slow React or browser flows.
 
@@ -10,7 +12,7 @@ When using the following skills, override the default behavior.
 
 `planning-with-files`:
 
-- Do not create `task_plan.md`, `findings.md`, or `progress.md` at repo root. Merge that content into one file under `.claude/docs/plans/`. Example: `.claude/docs/plans/2026-03-11-task.md`
+- Do not create `task_plan.md`, `findings.md`, or `progress.md` at repo root. Merge that content into one file under `docs/plans/`. Example: `docs/plans/2026-03-11-task.md`
 
 `dev-browser`:
 
@@ -27,7 +29,7 @@ When using the following skills, override the default behavior.
 
 - **Git:** Never git add, commit, push, or create PR unless the user explicitly asks.
 - **PR:** Before creating or updating a PR, run the local verification that actually matters here. At minimum: `bun run typecheck`, `bun run lint:fix`, and `bun run build` if the task touched app behavior or build config.
-- **plan:** Include test-browser in acceptance criteria for browser features.
+- **plan:** Include `dev-browser` in acceptance criteria for browser features.
 - **deepen-plan:** Context7 only when not covered by skills.
 - **work:** UI tasks require browser verification before marking complete. Never guess.
 

.agents/rules/1-app-design-document.mdc

@@ -0,0 +1,65 @@
+---
+description: Open a concise GitHub follow-up for reusable dev-browser or agent-browser limitations. Use when browser automation is blocked by a likely tool-side issue that is worth fixing separately, especially for clicks, dropdowns, file inputs, focus traps, or other repeatable agent/browser failures.
+argument-hint: '[browser block summary]'
+disable-model-invocation: true
+---
+
+# Agent Browser Issue
+
+Handle $ARGUMENTS.
+
+Use this only for likely reusable agent/browser tooling bugs. Do not use it for:
+
+- auth or SSO gates
+- manual human gates
+- product bugs on the site itself
+- one-off flaky noise with no minimal repro
+
+## Collect
+
+Capture only the minimum:
+
+- page or URL
+- action attempted
+- exact block
+- expected vs actual
+- minimal repro
+- screenshot only if it adds signal
+
+## Issue
+
+Open a GitHub issue with:
+
+- a short title focused on the browser/tool failure
+- label `agent:browser`
+- concise body
+
+Body shape:
+
+```md
+## URL
+<url>
+
+## Action
+<what the agent tried>
+
+## Block
+<what failed>
+
+## Expected
+<what should have happened>
+
+## Actual
+<what happened instead>
+
+## Repro
+1. ...
+2. ...
+3. ...
+```
+
+## After
+
+- if the browser/tool failure exposes a user-action parity gap, load `agent-native-reviewer` and note that gap in the issue
+- link the issue in the task caveat or handoff
+- keep moving if the product task is still otherwise fixable

.agents/rules/2-tech-stack.mdc

@@ -0,0 +1,124 @@
+---
+description: One-time setup for a persistent debug browser on `127.0.0.1:9222` for `dev-browser --connect`. Use when browser work is needed but no reusable debug browser is running yet.
+---
+
+# Browser Debug Setup
+
+Use this skill when `dev-browser --connect http://127.0.0.1:9222` fails because
+no persistent debug browser is running yet.
+
+## Goal
+
+Get the user onto one persistent browser/profile that both the human and the
+agent reuse. Minimize the `Allow remote debugging?` popup by keeping one
+dedicated debug browser/profile alive.
+
+## Rules
+
+- Prefer one permanent debug browser/profile over disposable automation
+  browsers.
+- Treat a custom `--user-data-dir` as mandatory, not optional. Chrome 136+
+  basically wants remote debugging to happen from a dedicated profile.
+- Keep auth in that profile. Do not fall back to cookie dumps or state files
+  unless the user asks.
+- Use a separate signed-in Chrome profile for browser work, like `dev`. Do not
+  use the user's normal daily `Default` profile as the source profile.
+- Clone that separate signed-in Chrome profile into the dedicated debug
+  `--user-data-dir`; do not point `9222` straight at the user's daily Chrome
+  data dir.
+- On macOS, use `open -na "Google Chrome" --args ...` for the debug browser.
+  That starts a separate Chrome instance with the dedicated debug profile
+  without touching the user's normal Chrome window.
+
+## Preferred Shape
+
+Use a dedicated browser/profile with:
+
+- `--remote-debugging-address=127.0.0.1`
+- `--remote-debugging-port=9222`
+- a persistent `--user-data-dir=<debug-profile-dir>`
+
+Sign in once in that dedicated browser and keep reusing it for agent work.
+
+Quick sanity check:
+
+```bash
+curl -sS http://127.0.0.1:9222/json/version
+```
+
+Healthy output includes a JSON object with `webSocketDebuggerUrl`. Empty output
+or `404` means the wrong process owns `9222`.
+
+Then verify `dev-browser`:
+
+```bash
+dev-browser --connect http://127.0.0.1:9222 <<'EOF'
+const page = await browser.getPage("persistent-main");
+console.log(await page.title());
+EOF
+```
+
+If `dev-browser --connect http://127.0.0.1:9222` still cannot resolve CDP even
+though `/json/version` is healthy, connect with the exact websocket URL:
+
+```bash
+WS=$(curl -sS http://127.0.0.1:9222/json/version | jq -r '.webSocketDebuggerUrl')
+
+dev-browser --connect "$WS" <<'EOF'
+const page = await browser.getPage("persistent-main");
+console.log(await page.title());
+EOF
+```
+
+## Google Chrome Path
+
+Default setup on macOS:
+
+1. Pick a separate signed-in Chrome profile for agent work, like `dev`, not
+   the daily `Default` profile.
+2. Map that human-facing Chrome profile name to the real folder in `Local State`.
+3. Clone that profile into the dedicated debug dir.
+4. Launch a separate Chrome instance on `9222`.
+5. Leave that debug window open and reuse it.
+
+```bash
+python3 - <<'PY'
+import json, pathlib
+p = pathlib.Path('~/Library/Application Support/Google/Chrome/Local State').expanduser()
+obj = json.loads(p.read_text())
+for key, val in obj.get('profile', {}).get('info_cache', {}).items():
+    print(f"{key}\tname={val.get('name')}\tgaia_name={val.get('gaia_name')}")
+PY
+
+# Example: if `dev` maps to `Profile 1`, clone `Profile 1`.
+mkdir -p "$HOME/.config/google-chrome-debug-profile/Default"
+rsync -a --delete \
+  --exclude='Singleton*' \
+  --exclude='DevToolsActivePort' \
+  --exclude='lockfile' \
+  "$HOME/Library/Application Support/Google/Chrome/Profile 1/" \
+  "$HOME/.config/google-chrome-debug-profile/Default/"
+cp "$HOME/Library/Application Support/Google/Chrome/Local State" \
+  "$HOME/.config/google-chrome-debug-profile/Local State"
+
+open -na "Google Chrome" --args \
+  --user-data-dir="$HOME/.config/google-chrome-debug-profile" \
+  --profile-directory="Default" \
+  --remote-debugging-address=127.0.0.1 \
+  --remote-debugging-port=9222
+```
+
+That keeps the signed-in identity while still satisfying Chrome's dedicated
+`--user-data-dir` requirement.
+
+Then keep reusing that exact debug browser. Do not point `9222` at your normal
+daily `Default` Chrome profile.
+
+## After Setup
+
+- Use `dev-browser --connect http://127.0.0.1:9222` for browser work.
+- Reuse named pages like `persistent-main`.
+- Do not stop the user's debug browser unless they ask.
+- If the wrong Chrome steals `9222`, identify it with `lsof -nP -iTCP:9222 -sTCP:LISTEN`,
+  kill that listener, and relaunch the dedicated debug browser. Do not keep
+  debugging against a stale `404` or empty `/json/version` owner.

.agents/rules/3-project-status.mdc

@@ -1,3 +1,7 @@
+---
+description: React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.
+---
+
 # Accessibility
 
 URL: /accessibility

.agents/rules/agent-browser-issue.mdc

@@ -0,0 +1,7 @@
+---
+description: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
+---
+
+Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
+
+If a question can be answered by exploring the codebase, explore the codebase instead.

.agents/rules/browser-debug-setup.mdc

@@ -0,0 +1,55 @@
+---
+description: Remove a feature completely with no backward compatibility. Use when the user says "hard cut", "rip it out", "delete it", "unship", "kill this feature", or wants dead code removed instead of deprecated. Delete the surface, callers, tests, docs, comments, fallbacks, and stubs.
+---
+
+# Hard Cut
+
+Use this when a feature should die, not linger.
+
+## Rules
+
+- Delete the surface. Do not deprecate it.
+- Do not leave `throw new Error("Not implemented")`, placeholder notices,
+  "feature removed" banners, or TODOs about bringing it back unless the user
+  explicitly asks.
+- Do not keep compatibility aliases, deprecated shims, fallback parsing,
+  migration bridges, or dead exports.
+- Delete tests for deleted behavior. Keep tests only for the behavior that
+  still exists.
+- Delete comments that describe deleted code or mourn the old feature.
+- If removal exposes adjacent dead code, keep cutting until the graph is clean.
+
+## Sweep
+
+1. Find the real surface area:
+   - exports
+   - commands and flags
+   - routes
+   - UI entrypoints
+   - feature flags
+   - docs and examples
+2. Trace references with `rg`.
+3. Delete the implementation and the glue:
+   - call sites
+   - types
+   - state
+   - tests
+   - docs
+   - comments
+4. Grep again for the removed name and obvious aliases.
+5. Run the narrowest honest verification for the surviving product.
+
+## Smells
+
+- deprecated notices
+- not-implemented throws
+- stub handlers
+- dead enum or union members
+- permanently-false feature-flag branches
+- unused env vars and config
+- tests that only prove the deleted feature used to exist
+
+## Bias
+
+If the choice is between deleting more code and leaving a zombie seam, delete
+more code.

.agents/rules/components.mdc

@@ -1,5 +1,4 @@
-# Default agents to apply when --agents flag is not specified
-default_agents = ["claude-code", "codex"]
+default_agents = [ "claude-code", "codex" ]
 
 [rules]
 merge_strategy = "cursor"
@@ -19,7 +18,7 @@ merge_strategy = "merge"
 
 [mcp_servers.plate]
 command = "npx"
-args = ["-y", "shadcn@latest", "mcp"]
+args = [ "-y", "shadcn@latest", "mcp" ]
 
 [agents.claude-code]
 enabled = true