production-workflow

A production-first coding workflow enforces structured task classification, repository inspection, controlled changes, and validation to ensure stability across app and web projects. It requires compiling code and docs, validating builds, and updating living documentation after each change.

To keep living docs synchronized, compress long-running context and update files like review.md, roadmap.md, and assessment.md after each meaningful code change. This ensures documentation accurately reflects the latest validated builds and flows.

Validating Vite builds requires compiling changes, inspecting repository truth, and executing end-to-end testing. A production-first workflow ensures deployments are validated before updating living docs like assessment.md for stable end-to-end flows.

Yes, this workflow applies explicitly to Flutter projects for refactoring, bug fixing, and auditing. It enforces controlled changes and validates outcomes before updating living docs, ensuring reliable end-to-end flows.

Fixing bugs in web repositories requires classifying the task, inspecting truth, applying controlled changes, and validating builds. Living docs must be updated to compress context and reflect the validated bug fixes.

Updating assessment.md after changes compresses long-running context into living docs, ensuring project status updates and end-to-end testing results remain synchronized with the actual codebase for continuous stability.