Documentation: fail-loud convention and config updates
Cluster 112020. Data as of
Nothing open on GitHub. Fix merged in #112235 on 16 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #112235. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #112235. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items add or update a 'fail-loud' convention for integration boundaries in CONTRIBUTING.md and align various documentation examples (config, cron watchdog, browser logins) with current code.
Open issues0
Open PRs0
Fixes on record
-
#112235 docs: config example, CONTRIBUTING conventions, cron watchdog and unattended browser logins now match the code (#111730, #112005, #112020, #111633, #111995, salvage #101327, #112037, #112024, #111636, #112001)
files:
CONTRIBUTING.md,cli-config.yaml.example,cron/AGENTS.md,website/docs/user-guide/features/browser.md,website/docs/user-guide/features/cron.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#112024 docs: add fail-loud boundary convention · merged via another change →
4179c5a,#112235
Closed issues · 1
- Closed#112020`CONTRIBUTING.md: a fail-loud convention for integration boundaries`
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #112235
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026