Ci workflow standardization#5
Merged
Merged
Conversation
Summary of changes: - Updated documentation (README, ADRs, Changelog) - Implemented runtime contract validation with Zod in NestJS - Migrated to versioned Prisma migrations - Fixed frontend tests and switched to Vitest - Hardened CI workflow with quality gates and native binding fixes
Summary of changes: - Created docs/RUNBOOK.md for operational guidance. - Rewrote apps/api and apps/web READMEs to remove boilerplate. - Expanded backend tests to cover duplicate, invalid, and auth_required scenarios. - Expanded frontend integration tests to cover DEAD_LETTER and network backoff logic. - Finalized doc alignment in docs/README.md by removing dead infra/db references.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Describe the change in 2-5 sentences.
Why this change exists
Explain the problem, gap, or failure mode being addressed.
Type of change
Affected areas
Behavior impact
What changes for users, contributors, or maintainers?
Reliability checklist
Complete this section if the PR touches queueing, retries, batching, deduplication, or API sync behavior.
IN_FLIGHTitems was considered.Testing
What did you run?
List commands and outcomes:
# paste commands hereScreenshots / logs / traces
Add relevant evidence when useful.
Documentation
Breaking changes
If breaking, explain migration or compatibility impact.
Linked issue
Closes #