tabs.js + docs: drop #272 + #275 cookies (#712 batch 8)

#272 (show approval requested-at — closed) ×2 in tabs.js (live
ApprovalAdded fallback note + amber stale chip comment) + ×1 in
docs/web-ui.md (Approval card identity header). #275 (select all
for meta inputs — closed) ×1 in tabs.js (bulk-select rationale)
+ ×1 in docs/web-ui.md (M3T4 1NPUTS tree control note). The
amber-stale chip line in tabs.js now points at
docs/web-ui.md::Approval card for the rendered spec instead of
the closed issue.

docs/web-ui.md

@@ -248,7 +248,7 @@ every fetched input at every depth (`hyperhive`,
 `hyperhive/nixpkgs`, `agent-<n>`, `agent-<n>/mcp-<x>`, …), each
 shown once at its shallowest path. `read_meta_inputs` walks the
 lock graph with a `visited` set — `follows` aliases and rev-less
-nodes are skipped (issue #275). A `select all / select none`
+nodes are skipped. A `select all / select none`
 control sits above the tree. Checking inputs + submitting bumps
 the lock in `/meta/` and rebuilds the selected agents in
 sequence; each outcome reaches the manager as a `rebuilt`
@@ -552,7 +552,7 @@ renderApprovals`) with three stacked sections:
   `apply_commit`) the short proposal sha as `<code>`, and a
   right-aligned `requested <N> ago` relative time from
   `ApprovalView.requested_at` — amber once the request has been
-  pending ≥ 1h so a stale approval stands out (issue #272).
+  pending ≥ 1h so a stale approval stands out.
 - **what-changed body** — the manager's description, then
   drill-in triggers: `↳ view diff` opens the diff in the side
   panel; `↳ commit on forge ↗` deep-links the proposal commit