chore(workers): eliminate 20 private-type-ref diagnostics from the published export surface

[rickylabs]

Summary

The published @netscript/plugin-workers export set currently produces 20 private-type-ref
diagnostics under the repository's full-export documentation lint. Publication dry-run remains a
separate gate, but a clean JSR documentation claim is not honest while these public signatures
resolve through private implementation types.

This is the durable owner for the pre-existing baseline discovered while planning #1378/#1545.
That quality-rail leaf must not absorb an unrelated Workers public-surface rewrite; it may record a
strict no-increase baseline linked here until this issue removes it.

Baseline

Measured on main 01e0960494c95ce56eb35892c211a095eb13e6ed on 2026-08-13:

deno task doc:lint --root plugins/workers --pretty
totalErrors: 20
totalPrivateTypeRef: 20
totalMissingJSDoc: 0
totalOther: 0
exitCode: 1

The auto-discovered surface contains 13 export targets. Eight currently contribute diagnostics:

Export target	private-type-ref
./bin/runtime.ts	9
./contracts/v1/mod.ts	7
./doctor.ts	1
./mod.ts	1
./services/src/main.ts	1
./streams/mod.ts	4
./streams/server.ts	7
./worker/mod.ts	3

Counts overlap because the same underlying private type can be reachable from multiple public
entrypoints; the repository reporter deduplicates the combined package total to 20.

Acceptance

• deno task doc:lint --root plugins/workers --pretty exits 0.
• Every one of the 13 auto-discovered export targets remains included; no export is hidden or
  removed merely to make the score green.
• Public signatures name stable exported contracts rather than private implementation aliases.
• deno publish --dry-run --allow-dirty remains green for the affected publishable members.
• Workers package/plugin tests and public-consumer checks remain green.
• The temporary no-increase debt entry created by the chore(quality): quality:scan cannot see an any in an exported type, an unbudgeted allowance, or a docs snippet #1378/chore(quality): register the pre-existing quality-allow population so #1378's linked-issue rule can land without a day-one red gate #1545 rail is closed.

Boundaries

• Do not weaken or erase public types to silence documentation lint.
• Do not fold this repair into chore(quality): quality:scan cannot see an any in an exported type, an unbudgeted allowance, or a docs snippet #1378/chore(quality): register the pre-existing quality-allow population so #1378's linked-issue rule can land without a day-one red gate #1545; that leaf may only preserve the exact baseline and prove
  it did not increase.
• Coordinate with Workers durable execution stream should publish typed progress #1592 if its typed progress work changes the same execution/stream contracts, but
  do not treat Workers durable execution stream should publish typed progress #1592 as satisfying this whole export-surface repair without the full lint proof.

Part of #1276. Discovered during 0.0.7 planning for #1378/#1545.

[rickylabs]

Coordinator baseline acceptance for the #1378/#1545 leaf: preserve a strict no-increase package total of 20 private-type-ref diagnostics across the same 13 auto-discovered Workers export targets. The quality rail may add a matching DEBT_ACCEPTED registry entry but may not claim this full-export gate green or absorb the repair. #1655 remains the removal owner in milestone 0.0.8.