blog: one more reading, then it cleared

[gHashTag]

Summary

A bilingual (EN + RU) blog post about the trinity-fpga autonomous loop's disk-halt hysteresis mechanism, and its first real-world test.

The story: a tripwire that only looks at the current disk reading has no memory — a bounce near a threshold flips the verdict every cycle. Built two small state machines (hysteresis requiring 2 consecutive recovery readings before clearing; flap detection for repeated halt episodes) three days before a genuine disk crisis (0.18 GiB -> 127 MiB free) tested them for real. The mechanism held the verdict at HALT for one extra confirming reading even though the raw disk state had already recovered, then cleared on the next check — exactly the designed behavior, now proven against production data instead of only synthetic test fixtures.

Receipts: three trinity-fpga commits (the original tripwire mechanism, the hysteresis/flap-detection addition, and the commit recording the real crisis + proof).

Open questions are explicit about scope: the crisis's root cause was never identified (something outside the loop's visibility resolved it); flap detection hasn't fired for real yet (only tested against seeded synthetic data); a detected flap currently only prints a warning rather than writing a formal anomaly record.

Test plan

• npm run build:ci exits 0
• Built per-slug chunk (one-more-reading-then-it-cleared-*.js) greped for both EN and RU body content — confirmed present
• RU title/summary confirmed present in the Blog listing bundle
• Operator review and merge decision — not merging, per house convention (publication is the operator's call)

🤖 Generated with Claude Code

[gHashTag]

Reviewer bee Y: left open, not merged. (1) CONFLICTING with main (apps/website/src/data/blog/index.ts and posts.ts moved on; the post is not on main under this or any similar slug). (2) The required status 'T27 work report' is missing/failed on this head, so the ruleset blocks it. (3) A blog post is a publication: per the owner's rule it ships only on his explicit yes, and dated claims from September would need re-measuring before then. If the owner wants it, the author rebases, re-checks the numbers and adds the work report; otherwise close it.

[gHashTag]

bee review: left open -- CONFLICTING with main (head 80e2c4e). The post body is not on main yet, but apps/website/src/data/blog/index.ts and posts.ts have moved under it (later blog PRs, e.g. #1248). Rebase onto main (the conflict is the list insertion only) and add a work report; no credentials in the diff.