chore(tooling): make .rustfmt.toml stable-honest; record CI/fmt findings

The .rustfmt.toml enabled nightly-only options (wrap_comments,
imports_granularity, group_imports, comment_width) while the build
toolchain is pinned stable 1.95 and the fmt job that would apply them
(pinned rust-toolchain.nightly via ci.yml) is not running — GitHub
Actions is not enabled on this fork (PR #29 head has zero check runs).
So those options were enforced by nothing yet made stable `cargo fmt`
warn and reformat divergently.

Comment them out so stable `cargo fmt` (the 1.95 pin, matching org
policy of 99% stable / nightly only for Miri) is the single authoritative
formatter. Re-enable as a block if a nightly-fmt CI job is ever turned on
and the tree is normalized under it in one dedicated pass.

Findings (no CI on the fork; rustfmt split-brain) recorded in
.claude/board/EPIPHANIES.md.

https://claude.ai/code/session_01R9AWgFa65uPnLyS2my2d2R

Author: claude

.claude/board/EPIPHANIES.md

@@ -114,3 +114,28 @@ previously reclaimed that space immediately).
 
 **Cross-ref:** codex P1 on PR #29 (discussion_r3328296248); fix in this
 commit; regression `test_timeline_write_delete_commit_is_single_atomic_version`.
+
+## 2026-05-30 — No CI runs on this fork; .rustfmt.toml is split-brain (stable build, nightly-only fmt opts)
+**Status:** FINDING
+**Scope:** repo CI/tooling — `.github/workflows/ci.yml`, `.rustfmt.toml`, `rust-toolchain*`
+
+PR #29 head (5997eea) has ZERO check runs; the only commit status is the
+CodeRabbit review bot (pending). `ci.yml` triggers on every `pull_request`
+(no branch filter), so the absence is environmental: GitHub Actions is not
+enabled/approved on the AdaWorldAPI fork. Net: the only merge gate is the
+review bots + the human owner — there is no test/clippy/fmt enforcement.
+Separately, `.rustfmt.toml` enables nightly-only options (wrap_comments,
+imports_granularity=Module, group_imports=StdExternalCrate, comment_width)
+while the build toolchain is pinned stable 1.95 (`rust-toolchain.toml`); the
+fmt-only nightly (`rust-toolchain.nightly` = nightly-2025-08-07) is never run
+here. Running fmt under either stable or that nightly reformats the WHOLE
+crate (~1900 lines, 22+ files) => HEAD is not fmt-clean under its own config.
+Consequence: "future-proof" config that no gate enforces is pure drift. Per
+the org's 99%-stable policy (nightly only for Miri in ndarray), the resolution
+is to make the config stable-honest (comment out the unstable opts) and lean
+on stable tools (cargo-machete et al.). A one-time stable `cargo fmt`
+normalization is a separate, deliberate follow-up (not triggered here, to
+avoid mixing mass reformat churn into feature commits).
+
+**Cross-ref:** PR #29 check status (0 runs); ci.yml on-block; this commit's
+`.rustfmt.toml` change; GRIDLAKE_BUILD.md.

.rustfmt.toml

@@ -7,15 +7,21 @@ use_field_init_shorthand = true
 use_small_heuristics = "Off"
 
 # -----------------------------------
-# Unstable options we would like to use in future
+# Unstable options (nightly-only rustfmt) — DISABLED.
+#
+# Org policy is 99% stable Rust (nightly is reserved for Miri in
+# `ndarray`). The job that would apply these — the pinned
+# `rust-toolchain.nightly` fmt in ci.yml — is not running (GitHub Actions
+# is not enabled on this fork), so these options were enforced by NOTHING
+# while still making stable `cargo fmt` warn and reformat divergently.
+# Commented out so stable `cargo fmt` (toolchain 1.95, per
+# rust-toolchain.toml) is the single authoritative formatter. Re-enable as
+# a block IF/WHEN a nightly-fmt CI job is turned on AND the tree is
+# normalized under it in one dedicated pass.
+# See .claude/board/EPIPHANIES.md (2026-05-30 CI/rustfmt finding).
 # -----------------------------------
 
-imports_granularity = "Module"
-#blank_lines_lower_bound = 1
-group_imports = "StdExternalCrate"
-#indent_style = "Block"
-#match_arm_blocks = true
-#reorder_impl_items = true
-wrap_comments = true
-
-comment_width = 100
+# imports_granularity = "Module"
+# group_imports = "StdExternalCrate"
+# wrap_comments = true
+# comment_width = 100