Skip to content

docs: expand contributor and integration guides#71

Merged
Bccorb merged 1 commit into
mainfrom
docs/contributor-and-integration-guides
Jul 7, 2026
Merged

docs: expand contributor and integration guides#71
Bccorb merged 1 commit into
mainfrom
docs/contributor-and-integration-guides

Conversation

@Bccorb

@Bccorb Bccorb commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Closes #63, closes #64, closes #65

Summary

Three documentation gaps from the usability survey, in one PR since they are all docs.

CONTRIBUTING.md (#63)

  • Testing section: run a single file/dir, the mock-vs-TEST_DB=postgres split, and a factory-based test-writing example.
  • What a good PR includes checklist: schemas + tests for routes, changeset for user-facing changes, license header, conventional commits, green checks, and calling out contract impact.
  • Pointer to docs/configuration.md.

docs/extending.md (#64)

  • Message-delivery providers: direct (SES/SNS/Twilio via directMessaging.ts) and external delivery mode, including the production service-token requirement.
  • How to add an endpoint (route → controller → service, schemas, auth).
  • Token-claim customization framed as a contract change (ripple protocol).
  • What is intentionally not extensible (token format, crypto primitives, response contract).

docs/api-contract.md (#65)

  • Which token comes from where (ephemeral/access/refresh), token shapes and access-token claims.
  • Branch-significant status codes per flow (e.g. magic-link poll 204 = pending; /refresh reads the refresh token from the Authorization header and rotates it).
  • Identifier-vs-email terminology clarified.

All request/response/claim details are taken from the route schemas and token.ts. New docs are linked from the README docs index and added to the docs/ gitignore allowlist.

Notes

Docs-only; no code or contract changes, no changeset.

- CONTRIBUTING.md: add Testing (single-test runs, Postgres e2e, factory
  example), a 'what a good PR includes' checklist, and a config pointer.
- docs/extending.md: message-delivery providers (direct + external),
  where custom behavior belongs, and what is intentionally not extensible.
- docs/api-contract.md: which token comes from where, token shapes/claims,
  branch-significant status codes, and identifier-vs-email terminology.
- Link the new guides from the README docs index and gitignore allowlist.

Closes #63
Closes #64
Closes #65
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@Bccorb Bccorb merged commit 94a0cfa into main Jul 7, 2026
2 of 3 checks passed
@Bccorb Bccorb deleted the docs/contributor-and-integration-guides branch July 7, 2026 19:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document the token and status-code contract per flow, and unify terminology Add an extensibility guide Expand CONTRIBUTING.md for new contributors

2 participants