docs(us3): record remaining service operational contracts - #85
Open
EstebanGZam wants to merge 3 commits into
Open
docs(us3): record remaining service operational contracts#85EstebanGZam wants to merge 3 commits into
EstebanGZam wants to merge 3 commits into
Conversation
This was referenced Aug 31, 2026
Merged
Record the verified frontend, todos-api, and users-api merge state, including the todos runtime packaging defect captured by the final SDD pair.
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
1 participant
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.
What changes
The authoritative full-platform task register now records the located,
verified, and merged frontend and users-api operational contracts. Its Phase 5
status also reconciles todos-api after its supply-chain and runtime-packaging
fixes merged, so all five service contracts are recorded as complete.
Why
The register still said frontend and users-api had not started, then described
frontend and todos-api as open after both had merged. Leaving that text
unchanged would make the SDD source of truth disagree with the reviewed
artifacts and CI evidence.
Paired implementation PRs:
Tasks
specs/009-full-platform-rolloutT073specs/009-full-platform-rolloutT076specs/009-full-platform-rolloutT078specs/009-full-platform-rolloutT081How it is verified
git diff --check— exit 0.completed=60,pending=102.6a76d90and7979ea6were observed failing before implementation; commit8369436passes lint, 8 tests, production build, audit, image build, and non-root runtime health/config/correlation checks. Commit4eb7066then remediates the PR-discovered OpenSSL CVE, and the CI-equivalent Trivy scan reports zero HIGH/CRITICAL findings.6bdf847.590b2e8and515fbdapreserve red operational and image-packaging evidence. The corrected image passes 17 tests, production audit, Spectral, non-root runtime smoke checks, and the CI-equivalent Trivy scan with zero HIGH/CRITICAL findings; PR test: retry todos production canary #15 merged as85b6944.42b22c8andae74775preserve the red test-first state; commit6b404fcpasses 13 Java 21 tests, Spectral, image build, and non-root runtime health/correlation/no-credential-log checks.6f00904.Risk and rollback
The risk is register drift if a merged service is reverted independently.
Rollback is to revert this PR's merge commit and reconcile against the then-live
service SHAs.
What this PR does not do
It does not deploy a service, accept US1 or US3, activate platform capabilities,
or perform Phase 4 cloud reads, plans, or applies.