docs: rebalance the README, plus a fixture dependency bump - #16
Merged
Conversation
Recording had grown to 110 lines, 26% of a 422 line README, and because it sat
inside Usage it pushed Contract Validation almost to the bottom.
Promotes Recording to its own top level section next to Contract Validation and
CI/CD, cuts the two explanatory subsections ("Pace versus speed" and "Why the
ending needs a hold") in favour of a link to the docs site, and adds a table of
contents so all three features are visible without scrolling.
The README keeps reference material only: the commands, the flags, the options
table and the not-a-CI-run warning. 422 lines down to 358, recording from 110
to 41. Nothing was lost: both cut sections were checked against the docs page
first, and the two details that were only in the README (the protocolTimeout
arithmetic and the deviceScaleFactor explanation) were added there.
TWD Contract Validation
23 passed · 41 failed · 3 warnings · 1 skipped Failed validations./contracts/users-3.0.json
./contracts/posts-3.1.json
./contracts/products-3.0.json
./contracts/events-3.1.json
|
twd-js only appears in test-example-app, the e2e fixture. The caret already resolved to 1.9.0, so this is the declared floor catching up rather than a functional change, but it makes the fixture honest about needing the pacing hook. The lock was regenerated with `npm install --package-lock-only` inside docker rather than on macOS, which strips the @emnapi entries the linux CI needs. Verified: 9 @emnapi entries before and after.
kevinccbsg
force-pushed
the
chore/readme-and-deps
branch
from
July 29, 2026 09:20
76c6b8d to
f5f1a2c
Compare
TWD Contract Validation
23 passed · 41 failed · 3 warnings · 1 skipped Failed validations./contracts/users-3.0.json
./contracts/posts-3.1.json
./contracts/products-3.0.json
./contracts/events-3.1.json
|
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.
Two related changes, both needed before a
1.4.1patch.Why a release is needed at all
npmjs.com renders the README from the published tarball, so the package page currently shows the pre-rebalance version. The fix only reaches users on a publish.
Worth noting: this is not about the
twd-js1.9.0 release. twd-cli has notwd-jsdependency, it was dropped in 1.3.0. The only reference is in the e2e fixture.1. README rebalance (
4e5e228)Recording had grown to 110 lines, 26% of a 422 line README, and because it sat inside
## Usageit pushed Contract Validation almost to the bottom. Contract validation is arguably the more differentiating feature and it read like an afterthought.Nothing was lost. Both cut sections were checked against the docs page first, and two details that existed only in the README (the
protocolTimeoutarithmetic and thedeviceScaleFactorexplanation) were added there before cutting. The dead#recording-a-runanchor in the config table is fixed.2. Fixture dependency bump (
f5f1a2c)twd-js^1.7.2^1.9.0test-example-appThe caret already resolved to 1.9.0, so this is the declared floor catching up rather than a functional change.
The lock was regenerated in docker, not on macOS, since
npm installthere strips the@emnapientries linux CI needs. Verified: 9@emnapientries before and after.Nothing in the root
package.jsonchanged.puppeteer^25.3.0to^25.4.0was available and deliberately left out: not enough value to justify shipping a browser automation bump in a docs release.Also outstanding in the fixture, left for their own sweep:
typescript~6.0.2to~7.0.2(a major),@types/node25 to 26,vite,react,react-dom,@types/react,@vitejs/plugin-react.Testing
308 passing, unchanged. Neither change touches runtime behaviour.