Decisions
Decision records - why a part of the workspace works the way it does, what else was considered, and what it costs.
A decision record explains one design choice that changed how a module behaves: the context, what was decided, the consequences and the alternatives that were turned down. Write one when a change needs more reasoning than a pull request description holds, and keep it once the change ships: the module pages describe how things work, the record why.
ESLint config
The shared ESLint flat config for Frigear packages and simple Node or Nuxt projects.
Session lifetimes per OAuth client
Why refresh-token lifetimes move from one global setting to a policy per application, how a first-party native app stays signed in for months, and what users and admins get to end those sessions.