Fix #6: finalize docs and production usage examples

[sam-parsons]

Summary

• Replace README planning notes with implementation-accurate documentation for current plugin behavior.
• Add a complete options reference (functions, debugger, labels, chainedCalls) plus copy-paste production usage.
• Document safe-removal vs chained/non-statement behavior with clear skip|warn|error outcomes.

Issues

• Fixes Issue F: Finalize docs and production usage examples #6

How to test

• npm run check
• npm run build

Notes

• Docs-only PR; no runtime behavior changes.
• Source-map emission work in Issue G: Emit source maps for transformed output #9 is intentionally deferred until after this docs finalization.

---

Learning notes

Conservative stripping as an operational safety choice

What it is
When a transformation cannot prove a removal is behavior-preserving, it should prefer explicit policy over best-guess mutation.

Where it appears in this PR
The README now mirrors the plugin's call-line analysis behavior by distinguishing whole-statement removals from chained/non-statement matches and mapping those to chainedCalls policies.

Why it was the right call here
An aggressive strip strategy could remove code that still contributes runtime behavior (for example, chained expressions). The chosen approach keeps removals deterministic and safe by default (skip), while allowing teams to raise strictness (warn or error) as part of CI policy.