mirror of
https://github.com/zvx-echo6/meshai.git
synced 2026-06-11 01:14:45 +02:00
fix(v0.6-tail-2): finish Quiet Hours rip (Reference.tsx + dashboard bundle rebuild)
Phase 2 (b948ed7) stripped Notifications.tsx + backend config + pipeline
checks but missed Reference.tsx, which has live documentation describing
Quiet Hours as if it still exists. Per feedback-quiet-hours-trash.md the
intent is removal, not refactor -- the Reference page tells users about
a feature that does not exist. Strip the SectionHeader Quiet Hours block
(lines 952-956) and the quiet-hours clause from the rules-evaluation
checklist (line 922). Rebuild dashboard bundle so the JS no longer
contains the strings.
Reference.tsx changes:
- Line 922 rules-evaluation checklist: drop the 'Are we in quiet hours?'
clause from the 'MeshAI checks your rules' bullet.
- Lines 952-956 deleted: the SectionHeader 'Quiet Hours' + the two
paragraphs explaining 10pm-6am suppression and the 'Override Quiet
Hours' rule flag.
Other 'Quiet' matches in Reference.tsx are SFI/Kp solar terminology
('Quiet sun', 'Quiet. Best HF conditions.') and remain untouched --
unrelated to quiet hours.
Dashboard bundle rebuilt via vite. New artefacts:
meshai/dashboard/static/assets/index-WV9oBF1j.js (2,145.58 kB)
meshai/dashboard/static/assets/index-j88L17ja.css (45.08 kB)
Verification:
grep -rln 'quiet hours|quiet_hours|quietHours|override_quiet|Override Quiet' dashboard-frontend/src
-> 0 hits
grep -ic 'quiet hours|override.quiet|quiet_hours|quietHours' index-WV9oBF1j.js
-> 0 hits
Side artefact (not in commit): independent verification of Central
v0.10.2 Spokane-class leak fix completed today; all four meshai-side
checks pass (config audit, JetStream subscribe, event_log breakdown,
mesh_broadcasts_out scan). Report at OneDrive:
v0.6-tail-2-spokane-verify.md. No meshai-side code change needed.
This commit is contained in:
parent
566b06de06
commit
24763947c3
3 changed files with 3 additions and 9 deletions
|
|
@ -919,7 +919,7 @@ export default function Reference() {
|
|||
<SectionHeader>How It Works</SectionHeader>
|
||||
<ol className="list-decimal list-inside ml-4 space-y-1">
|
||||
<li><strong>Something happens</strong> — a fire is detected, weather warning issued, node goes offline, etc.</li>
|
||||
<li><strong>MeshAI checks your rules</strong> — does this event match any of your notification rules? Is it severe enough? Are we in quiet hours?</li>
|
||||
<li><strong>MeshAI checks your rules</strong> — does this event match any of your notification rules? Is it severe enough?</li>
|
||||
<li><strong>If a rule matches</strong> — MeshAI sends the notification through whatever delivery method that rule is configured for.</li>
|
||||
</ol>
|
||||
|
||||
|
|
@ -949,12 +949,6 @@ export default function Reference() {
|
|||
<strong>"Warning" is the sweet spot for most rules.</strong> You get alerted when something actually needs your attention without being overwhelmed by every minor event.
|
||||
</p>
|
||||
|
||||
<SectionHeader>Quiet Hours</SectionHeader>
|
||||
<p>
|
||||
When enabled, non-emergency notifications are held during sleeping hours (default 10pm-6am). Emergency alerts and rules marked "Override Quiet Hours" always get through.
|
||||
</p>
|
||||
<p>You can turn quiet hours off entirely if you don't want them.</p>
|
||||
|
||||
<SectionHeader>Webhook — The Swiss Army Knife</SectionHeader>
|
||||
<p>
|
||||
A webhook sends your alert as an HTTP POST to any URL. This one delivery method works with:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue