test: guard published content estimate examples
The published-command guard ran maintained email/song examples but missed both content-estimate examples. Add them to the compiled CLI guard, preserve query strings in the synthetic request recorder, and assert GET, no body, and exact default/explicit lipsync, batch and compare values.
Validation at a30e901526ffbd1f04a959dbc11d35aa1855e0c9: clean Node22 CI40158324013 passes typecheck, build and all83tests/13files. Local focused6/full83 pass. Deliberate removal of --compare from the guide and a temporary GET-to-POST parser mutation fail at the intended assertions; restored source passes. Requests remain origin-fenced and non-forwarding with synthetic credentials. Independent Standards:0 findings; Spec:0 findings.
Part of recoupable/mono#360 and the existing #355 estimate-example criterion. Three test/fixture files only; runtime, version, dependencies and publishing workflow unchanged. Does not verify actual prices, content creation, npm publication or installed-client behavior. Coordinator owns merge; the normal CLI push-main publisher and its existing access prerequisite remain separate. Marketing should adopt the actual merged guard commit through a subsequent reviewed pin update.
Summary by CodeRabbit
- Documentation
- Added cost-estimate examples and clarified which request details are retained or omitted.
- Tests
- Added checks confirming the examples send GET requests with the expected estimate options and no request body. The examples also verify that query parameters are preserved in request records.