Issue #79 write-ups, Watchtower settings pair, browser extension dev guide
Six new pages and five updated.
New:
- Issue-79-Ticket-Status-Not-Set — the reported status fault. Seven
creation paths, the priority that survived because "Normal" is the same
word in German, and the header fallback that displayed "Open" BECAUSE
no status was stored.
- Issue-79-Ticket-Source-Not-Set — the other half of the same report.
Why it could not be a one-line fix (ticket_origins has no is_default
and is company-scoped), the per-mailbox dropdown that dissolved it, and
the dismissible health mark.
- Configurable-Lookups-Developer-Guide — the through-line. Thirty-plus
places across five modules, three of them wrong in English on a stock
install; what to read instead of a name; the two derivations; the
"don't borrow a domain fact for a view decision" rule; and the
whole-payload rename diff that proves a fix.
- Watchtower-Settings + Watchtower-Settings-Developer-Guide — the pair.
- Browser-Extension-Developer-Guide — the endpoint, the payload keys, and
the trap of being the second consumer of a shared payload.
Updated:
- Watchtower — was describing eight cards and metrics that no longer
exist; now ten, with the settings link.
- Browser-Extension — corrected the badge description, added the update
notice and the dev guide link.
- Mailbox-Authentication — the Default ticket origin and the ! mark,
including why warnings can be dismissed and errors cannot.
- Bugs-Resolved — three rows.
- _Sidebar — nested entries under Watchtower, Browser Extension and Bugs
resolved.
Both validations clean across all 190 pages: every [Link] resolves to a
real .md, and every backticked path exists in the repo. Seven bare
filenames were promoted to full paths, as on the Forms and Slack pairs.