docs: align overviews with the complete 11/11 API surface#99
Merged
Conversation
After v1.0.12–v1.0.14 (developer-registration, conversions, lfp) the full Merchant API surface is covered. Update the narrative docs that lagged: README Phase 10 row + breadth note, the landing-page typed-API card, the guide Status section (was 'v1.0.0 / nine phases / 9 commands'), and the roadmap Phase 10 row + narrative — all now reflect all 11 sub-APIs covered.
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
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.
Aligns the narrative docs that lagged behind v1.0.12–v1.0.14 (developer-registration, conversions, lfp). The Merchant API surface is now fully covered (11/11 sub-APIs), so the overviews now say so:
conversions+lfp, marked Done,v1.0.2–v1.0.14) and the breadth note ("all 11 sub-APIs now covered").Docs-only — no code, no changeset. Deploys via the docs workflow on merge.