What this is
The public /try page runs labelled detection and a static source inventory in your browser tab. It uses the same guest WASM bytes as the published SDK for fixture detection. Files stay in the tab. Nothing is uploaded to AGINDOW servers. This is observe-mode detection evidence and non-authoritative scan output — not production protection and not an applied repair.
1. Run the labelled sample
On /try, under Fixture detection, click Run sample. The page loads the guest WASM only when you run. Expect two panels: Changed window (sample) shows a finding for the labelled numeric magnitude shift (baseline value 1 → live value 100), typically with detector Unit and class semantic; Unchanged window (control) shows no drift. Status text may briefly say the guest is loading. Timing and latencyUs can vary; the finding fields are the stable evidence.
2. Optional custom fixtures
Caps: at most 5 text/JSON files, ≤256 KiB each, ≤1024 KiB total. Use Choose fixtures then Run fixtures, or paste fixture JSON into the textarea and run. Binaries, oversize sets and a sixth file are rejected. A result that mentions repair or block is dry-run only — proposed, not applied; no upstream call. The default guest has no selective repair output.
3. Scan source inventory
Under Source inventory, paste source in the TypeScript or Python tab (docs-style token colors — not IntelliSense) or Choose source files, then click Scan source. Inventory parses TypeScript/JavaScript only; a Python-only paste explains that limit and points to Quickstart for Python detection. This path does not load the guest WASM; it loads a separate scanner chunk in-tab. Expect a Scan summary with tools detected, wrap call sites (hint only), vendors and skipped files. Wrap hints never mean protection is on, writes are guarded, or config is effective. A static scan alone never grants protection.
4. What not to expect
No code execution of your paste beyond the static inventory parse, no registry snapshot, no applied selective repair, no vendor credentials, and no hosted write protection. Installing the SDK alone also does not detect drift — configure a detector with baseline/live windows after you leave the playground.
5. Install and detect
When you are ready to run the same labelled detection outside the browser, follow Quickstart for the pinned npm/PyPI install and the Node detect sample.