Who holds the client secret?
When a desktop CLI posts on your behalf, the OAuth tutorial assumption of a server holding the client secret collapses. What replaces it.
Tags
36 pages
Architecture
The component that fired on every schedule
A CI component gated on the default branch fired on every Renovate schedule too, because a scheduled run is also on the default branch.
Release trust without the framework
Two new public modules extracting the OpenPGP signing and verification model, so you can use it without adopting the whole framework.
Telemetry that asks, and telemetry that doesn't
Two telemetries with opposite consent defaults on one OTLP layer: consent-gated analytics for a CLI, implied-consent observability for a service.
One graph, not micro-stacks
Why an infrastructure repo stays one OpenTofu graph rather than splitting into per-concern stacks: the engine enforces ordering for free.
Why I hand-rolled every module
Why security-critical infrastructure got raw resources rather than community wrapper modules, and what that actually cost in lines and in review.
Supporting a provider, or actually using it
A lowest-common-denominator AI interface throws away what each provider is good at. When to route through an abstraction and when to drop below it.
Two kinds of feature flag
Runtime feature flags decide which commands are reachable on a given run. Cargo features decide what is compiled in at all. Do not confuse them.
Reloading config without a restart
Hot-reloading configuration: watch the file, re-read it, swap it in atomically and notify observers, without restarting a long-running service.
Registering commands without life before main
Rust has no init or pre-main phase, so self-registering commands need another mechanism. Using a distributed slice to get the same shape.
