feat(crates): trios-igla-ops — O(1) operator utilities (Rust, R1)

[gHashTag]

Summary

New workspace crate crates/trios-igla-ops with 3 Rust binaries replacing the ad-hoc Python / bash ops scripts the operator asked to remove. Rule R1 from trios#143: Rust-only, O(1) — every tool solves its task in a single call.

Binaries

bin	purpose	call cost
fleet-probe	parallel auth + health for all 7 Railway accounts	7 GraphQL calls, fanned out via tokio; ~1 s wall
queue-stats	mission snapshot (queue counts, running by lane, active scarabs, best-BPB leaderboard top-15)	1 Neon connection, 4 queries
queue-victory-hunt	idempotent insert of 480-row victory-hunt grid (LR8 × h6 × F17..F21 × binary32/GF16)	1 Neon connection, single transaction

Modules

• accounts.rs — canonical 7-account registry keyed by RAILWAY_TOKEN_ACC{0..6} env. Lane mapping per trios#445. SANCTIONED_SEEDS = F17..F21 matches the enforce_seed_policy() trigger in Neon.
• neon.rs — strip_channel_binding (rustls 0.23 cannot satisfy SCRAM-PLUS, see trios-trainer-igla#84 round 3) + idempotent CryptoProvider install + connect() wrapper.

Canon enforcement

All canon_names produced follow the mandatory-format spec from trios-trainer-igla#93:

IGLA-{LANE}-{format}-h{H}-LR{LR4}-rng{SEED}-{TAG}

where {format} is drawn from the 60+ format catalog (zig-golden-float#69) and never omitted.

Verification

• cargo test -p trios-igla-ops --lib — 3/3 GREEN (strip_channel_binding unit tests)
• cargo build --release -p trios-igla-ops — 3 binaries clean
• queue-stats smoke against live Neon DSN-A: 493 pending IGLA-* rows, 30 running, 9 IGLA-RAILWAY-* scarabs heart-beating

Usage

source .railway_creds.env
cargo run --release -p trios-igla-ops --bin fleet-probe
cargo run --release -p trios-igla-ops --bin queue-stats
cargo run --release -p trios-igla-ops --bin queue-victory-hunt

References

• trios#143 — IGLA RACE master, R1 Rust-only
• trios#445 — 6-account lane canon (LEADER + FOLLOWER-A..E)
• trios-trainer-igla#84 — telemetry restoration (5-round fix)
• trios-trainer-igla#93 — canon_name format spec
• zig-golden-float#69 — 60+ numeric format catalog

🌻 phi^2 + phi^-2 = 3 · TRINITY · NEVER STOP

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
31559427	Triggered	PostgreSQL Credentials	25713f6	crates/trios-igla-ops/src/neon.rs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}