docs: capture apps/editor dev-workflow and CSS gotchas from this session

Recurring friction points worth not rediscovering next time: the dev
server's static files (index.html/styles.css) aren't watched and need a
manual copy after every edit; the [hidden] attribute silently loses to
any author display: rule unless scoped :not([hidden]) (hit repeatedly
this session on different elements); native date/time inputs have a
Chrome rendering-width floor CSS can't shrink below; triggering a native
confirm()/beforeunload dialog via the computer tool blocks the whole
browser-automation session until dismissed; and OTE's spec has no
recurrence-rule concept at all (one document per occurrence, always).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DrGeVXHTNNdPi7MCgSageG

Author: hhkaos

CLAUDE.md

@@ -23,3 +23,6 @@ Central monorepo for the OTE organizer kit. Read DESIGN.md before any task.
   `pnpm build` has run. That error means the workspace is unbuilt, not broken —
   never "fix" it by touching imports. CI never hits it: it builds first.
 - Convention: connectors never invent data; absent field = absent + warning.
+- `apps/editor` has its own `CLAUDE.md` — dev-workflow gotchas (static
+  files aren't watched), a recurring CSS `:not([hidden])` pitfall, and
+  browser-testing notes specific to that app. Read it before editor work.

apps/editor/CLAUDE.md

@@ -0,0 +1,57 @@
+# apps/editor
+
+Vanilla TypeScript + DOM event editor (no framework). `main.ts` bundles
+via esbuild to `dist/main.js`; `index.html`/`styles.css` are static files
+copied into `dist/`.
+
+## Dev workflow gotcha
+
+`pnpm dev` (esbuild watch + static server) only rebuilds `dist/main.js`
+on save. `index.html` and `styles.css` are copied into `dist/` **once**,
+at server startup — they are not watched. After editing either, run:
+
+    cp apps/editor/index.html apps/editor/styles.css apps/editor/dist/
+
+before reloading the browser, or you'll be looking at stale markup/CSS.
+
+## CSS: the `hidden` attribute loses to author `display` rules
+
+Any CSS rule that sets `display:` on a selector that's *also* toggled via
+the JS `hidden` property must be scoped `:not([hidden])`. An author
+stylesheet rule always wins over the UA stylesheet's `[hidden] { display:
+none }`, regardless of specificity — so a plain `.foo { display: flex }`
+silently defeats `fooEl.hidden = true` elsewhere. Bitten by this
+repeatedly in the same session: `#profile-switch`, `.recurrence-fields`,
+`.field.pair`. When adding a new `display:` rule on anything toggled by
+`.hidden = …` in `main.ts`/`ui/form.ts`, default to `:not([hidden])`.
+
+## Native date/time inputs have a rendering-width floor
+
+`<input type="date">`/`<input type="time">` won't shrink below their own
+intrinsic minimum width in Chrome, regardless of `flex-basis`/`width`
+CSS. Cramming 4-5 of them into a narrow flex row (e.g. inside a
+`.repeater-item`) may still wrap even with generous CSS budgeting — a
+real platform constraint, not a CSS bug worth chasing further.
+
+## Browser-testing this app: avoid getting stuck on confirm()/beforeunload
+
+The app calls `window.confirm(...)` before discarding a pending import
+queue or replacing form content, and has a `beforeunload` handler
+guarding unsaved changes. Both are **native browser dialogs** — triggering
+one via the `computer` tool's click action blocks the whole
+Claude-in-Chrome session (CDP calls time out) until dismissed.
+- Before clicking anything that might trigger a confirm(), stub it first
+  via `javascript_tool`: `window.confirm = () => true;`
+- If a `beforeunload` "Leave site?" dialog gets stuck anyway, recover by
+  calling `navigate` again with `force: true` — it discards the dialog
+  and proceeds.
+
+## OTE has no recurrence-rule concept
+
+The spec is explicit: one document per occurrence, always ("un documento
+= una ocurrencia. Quien publica expande."). Never store a rule in an
+event/feed file — a "repeat" feature must *generate* N documents, not
+represent recurrence as data. The spec's own guidance for an otherwise
+open-ended series: expand a bounded horizon ("12 meses o las próximas 12
+ocurrencias"), not forever — `lib/recurrence.ts`'s `MAX_OCCURRENCES` caps
+every generated series at 24 for this reason.