Fix the build, and the review's findings

The gate caught a real dash, just not one of mine: main released 0.4.0
while this branch was open, and the audit-log entry it wrote into both
CHANGELOG.md files carries an em-dash. CI builds the merge commit, so it
saw a changelog my local build did not. Rebased onto main and spelled
that entry's pause with a comma.

From the review:

Nested main landmarks. The docs layout opened a <main> around the column
and another around the outlet. The inner one is an <article> now.

Internal links reloaded the document. Everything on the site routes
through md's A, and it rendered a plain anchor for every href, so moving
between pages threw away the router and started again. App-relative
hrefs go through TanStack's Link; mailto and off-site stay anchors.

The command reference built a scroll box per usage line, forty of them
down the page, each one hiding its tail from anyone not using a pointer.
The usage wraps instead, indented under the command.

"Every command takes --tab, --browser and --json" was not true: status,
doctor, kill and help take none of them. Scoped to the commands that act
on a page or a tab, in the README, on the homepage, in the getting
started page, in the command reference, and in llms.txt.

A blank line in a transcript is a space so the row keeps its height, and
it is now aria-hidden rather than announced as spoken content.

Not taken: the suggestion to rename browserId to --browser in the
daemon's error messages. It is a fair point about naming, but those
strings are CLI behaviour that tests assert on, and this branch only
touched them to remove dashes. It belongs in its own change.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: karngyan

README.md

@@ -55,8 +55,9 @@ reins click --ref e5        # act: by ref
 reins text                  # check: or reins screenshot, which prints an image path
 ```
 
-Every command takes `--tab <id>` (default: active tab), `--browser <id>` (only
-when several are connected), and `--json`. `reins help` is self-describing, and
+Shared flags, on the commands that act on a page or a tab: `--tab <id>`
+(default: active tab), `--browser <id>` (only when several are connected), and
+`--json` for raw output. `reins help` is self-describing, and
 `reins cdp` reaches the full Chrome DevTools Protocol when the curated commands
 are not enough.
 

packages/cli/CHANGELOG.md

@@ -4,7 +4,7 @@
 
 ### Minor Changes
 
-- 65ce7f3: `reins audit` — a per-action audit trail. The extension stamps each response with the resolved host, permission tier, and tab; the daemon writes one redacted JSONL line per action (policy denials included) to `~/.reins/logs/audit-YYYY-MM-DD.jsonl`, pruned after 30 days. Value-bearing params (typed text, fill values, eval code, CDP payloads) are redacted before anything reaches disk.
+- 65ce7f3: `reins audit`, a per-action audit trail. The extension stamps each response with the resolved host, permission tier, and tab; the daemon writes one redacted JSONL line per action (policy denials included) to `~/.reins/logs/audit-YYYY-MM-DD.jsonl`, pruned after 30 days. Value-bearing params (typed text, fill values, eval code, CDP payloads) are redacted before anything reaches disk.
 
 ## 0.3.0
 

packages/extension/CHANGELOG.md

@@ -4,7 +4,7 @@
 
 ### Minor Changes
 
-- 65ce7f3: `reins audit` — a per-action audit trail. The extension stamps each response with the resolved host, permission tier, and tab; the daemon writes one redacted JSONL line per action (policy denials included) to `~/.reins/logs/audit-YYYY-MM-DD.jsonl`, pruned after 30 days. Value-bearing params (typed text, fill values, eval code, CDP payloads) are redacted before anything reaches disk.
+- 65ce7f3: `reins audit`, a per-action audit trail. The extension stamps each response with the resolved host, permission tier, and tab; the daemon writes one redacted JSONL line per action (policy denials included) to `~/.reins/logs/audit-YYYY-MM-DD.jsonl`, pruned after 30 days. Value-bearing params (typed text, fill values, eval code, CDP payloads) are redacted before anything reaches disk.
 
 ## 0.3.0
 

packages/web/public/llms.txt

@@ -9,7 +9,7 @@ Key facts:
 - Core loop, in three beats. Look: `reins snapshot` lists interactive elements with refs. Act: `reins click --ref e7` or `reins type --ref e3 --text "…"`. Check: `reins text` or `reins screenshot`.
 - Site permissions: every site resolves to a tier, one of deny, read, or full. The extension enforces it. Grants happen only through a click in the extension popup, and the CLI can tighten the policy but never loosen it.
 - Security: the daemon binds 127.0.0.1 and validates the Host header. Only allowlisted chrome-extension:// origins may connect. Chrome shows its native debugging banner the whole time the extension is attached.
-- Limits: Chromium only, so no Firefox and no WebKit. No headless mode. Not built for CI. With two browsers connected, commands need `--browser <id>`, because reins never guesses which one you meant.
+- Limits: Chromium only, so no Firefox and no WebKit. No headless mode. Not built for CI. With two browsers connected, the commands that act on a page or a tab need `--browser <id>`, because reins never guesses which one you meant.
 
 ## Docs
 

packages/web/src/components/md.tsx

@@ -1,3 +1,4 @@
+import { Link } from "@tanstack/react-router";
 import type { ReactNode } from "react";
 import { cn } from "@/lib/utils";
 
@@ -107,13 +108,30 @@ export function Ol({ children }: { children: ReactNode }) {
   );
 }
 
+const LINK_CLASS = "underline underline-offset-4 hover:text-primary";
+
+/**
+ * Every link on the site.
+ *
+ * An app-relative href routes through TanStack's `Link`, so moving between
+ * pages does not reload the document and lose the router. Everything else
+ * (http, mailto, and any other scheme) is a plain anchor, and anything
+ * off-site opens in its own tab.
+ */
 export function A({ href, children }: { href: string; children: ReactNode }) {
+  if (href.startsWith("/")) {
+    return (
+      <Link to={href} className={LINK_CLASS}>
+        {children}
+      </Link>
+    );
+  }
   const external = href.startsWith("http");
   return (
     <a
       href={href}
       {...(external ? { target: "_blank", rel: "noreferrer" } : {})}
-      className="underline underline-offset-4 hover:text-primary"
+      className={LINK_CLASS}
     >
       {children}
     </a>
@@ -167,10 +185,12 @@ export function Shell({ lines }: { lines: string[] }) {
         // Lines repeat in a transcript (blank ones, at least), so the index
         // is the only key that is honest.
         // biome-ignore lint/suspicious/noArrayIndexKey: transcript lines are not unique
-        <span key={i} className="block">
+        <span key={i} className="block" {...(line === "" ? { "aria-hidden": true } : {})}>
           {line === "" ? (
             // An empty block has no height, so a blank line in the transcript
-            // would vanish. A space under `whitespace-pre` keeps the line.
+            // would vanish. A space under `whitespace-pre` keeps the line, and
+            // the row is hidden from assistive tech so it is not announced as
+            // a spoken space.
             " "
           ) : line.startsWith("$") ? (
             <>

packages/web/src/routes/docs/commands.tsx

@@ -161,7 +161,10 @@ const GROUPS: Array<{ id: string; title: string; intro?: string; rows: [string,
 function Command({ usage, summary }: { usage: string; summary: string }) {
   return (
     <div className={cn(TEXT, "mt-5 max-w-[68ch]")}>
-      <p className="overflow-x-auto whitespace-pre">{usage}</p>
+      {/* Wraps rather than scrolls. A scroll box per command would be forty
+          keyboard stops down the page, and a long flag list is still legible
+          broken across lines when the wrap is indented under the command. */}
+      <p className="whitespace-pre-wrap [text-indent:-2ch] pl-[2ch]">{usage}</p>
       <p className="text-pretty text-muted-foreground">{summary}</p>
     </div>
   );
@@ -172,10 +175,12 @@ function CommandsPage() {
     <>
       <H1>Commands</H1>
       <P>
-        The CLI is the whole interface: agents shell out to it, and so can you. Every command
-        accepts <Code>--tab &lt;id&gt;</Code> (the active tab by default),{" "}
-        <Code>--browser &lt;id&gt;</Code> (only needed when several browsers are connected, and the
-        ids come from <Code>reins tabs</Code>) and <Code>--json</Code> for raw results.
+        The CLI is the whole interface: agents shell out to it, and so can you. The commands that
+        act on a page or a tab share three flags: <Code>--tab &lt;id&gt;</Code> (the active tab by
+        default), <Code>--browser &lt;id&gt;</Code> (only needed when several browsers are
+        connected, and the ids come from <Code>reins tabs</Code>) and <Code>--json</Code> for raw
+        results. The management commands (<Code>status</Code>, <Code>doctor</Code>,{" "}
+        <Code>kill</Code>, <Code>help</Code>) take none of them.
       </P>
       {GROUPS.map((group) => (
         <Fragment key={group.id}>

packages/web/src/routes/docs/index.tsx

@@ -79,9 +79,9 @@ function GettingStarted() {
         ]}
       />
       <P>
-        Every command accepts <Code>--tab &lt;id&gt;</Code> (the active tab by default),{" "}
-        <Code>--browser &lt;id&gt;</Code> (only needed when several browsers are connected) and{" "}
-        <Code>--json</Code> for raw output.
+        The commands that act on a page or a tab share three flags: <Code>--tab &lt;id&gt;</Code>{" "}
+        (the active tab by default), <Code>--browser &lt;id&gt;</Code> (only needed when several
+        browsers are connected) and <Code>--json</Code> for raw output.
       </P>
       <Arrow href="/docs/commands">Full command reference</Arrow>
       <Arrow href="/docs/architecture">How the pieces fit together</Arrow>

packages/web/src/routes/docs/route.tsx

@@ -43,9 +43,11 @@ function DocsLayout() {
             <CopyMarkdown contentRef={contentRef} className="ml-auto" />
           </p>
 
-          <main ref={contentRef} data-pagefind-body className="mt-10">
+          {/* An article, not a second <main>: the layout above already opens
+              one, and two main landmarks on a page is one too many. */}
+          <article ref={contentRef} data-pagefind-body className="mt-10">
             <Outlet />
-          </main>
+          </article>
 
           <Rule />
           <p className={cn(TEXT, "mt-5 text-muted-foreground")}>Other pages</p>

packages/web/src/routes/index.tsx

@@ -179,9 +179,10 @@ function Loop() {
     <>
       <H2 id="loop">The loop</H2>
       <P>
-        Every page interaction is the same three beats: look, act, check. Every command takes{" "}
-        <Code>--tab &lt;id&gt;</Code> (the active tab by default), <Code>--browser &lt;id&gt;</Code>{" "}
-        (only when more than one browser is connected) and <Code>--json</Code>.
+        Every page interaction is the same three beats: look, act, check. The commands that act on a
+        page or a tab share three flags: <Code>--tab &lt;id&gt;</Code> (the active tab by default),{" "}
+        <Code>--browser &lt;id&gt;</Code> (only when more than one browser is connected) and{" "}
+        <Code>--json</Code> for raw output.
       </P>
       <Shell lines={LOOP_LINES} />
       <Arrow href="/docs/commands">Full command reference</Arrow>