Engineering Notes

Release context, implementation decisions, and technical tradeoffs.

A running log of product decisions behind MockForge, from scenario modeling and test hardening to release safety and client generation tradeoffs.

March 5, 2026

Release Engineering Note: Security Guardrails from v0.2.x

A focused review of v0.2.x hardening work: validation defaults, auth-related flow safety, and migration priorities for teams upgrading from earlier versions.

March 3, 2026

How We Use Scenario Switching to Keep Mocks Honest

Scenario switching helps teams test stateful behavior instead of static happy-path fixtures. This note outlines a practical scenario model and why it improves integration confidence.

January 21, 2026

Release Cadence and Risk: How We Keep Fast Iteration Safe

How we sequence fixes, hardening, and communication so release speed does not become release risk.

December 10, 2025

Client Generation Tradeoffs: Safety, Speed, and Developer Experience

A practical note on balancing strict schema fidelity with developer velocity in generated clients.

November 5, 2025

Why Failure-Path Testing Should Be a First-Class Mocking Requirement

Controlled failure profiles expose retry and fallback weaknesses before integration surprises hit teams.

October 8, 2025

Migration Guide: Moving from Static Fixtures to Stateful Mocks

A staged migration path from static fixtures to state-aware scenario switching for better integration confidence.

Want release notes in product context instead of changelog fragments? Start with the notes here, then jump into the full docs for commands, schemas, and migration detail.