# Feature inventory and completion boundaries

## Authored and implemented

| Resource | Delivered |
|---|---:|
| Selectable lessons / modules | 100 / 20 |
| Runnable worked-example slots | 300 |
| Independently launchable visual objects | 40 |
| Coding activities | 200, ten per module |
| Reproducible debugging investigations | 150 |
| Knowledge questions | 250 |
| Complete applications | 30 |
| Complete starter file sets | 30 |
| Glossary definitions | 250 |
| Prepared contextual prompt templates | 300 |
| Directly launchable demonstration scripts | 20 |
| Static printable lesson pages | 100 |

Examples reuse a few relevant patterns across different lessons; the count is of authored worked-example slots, not a claim that each program is a unique algorithm. Each lesson has a practical concept explanation, three examples, source walkthroughs, prediction, editable exercise, exact checks or DOM behavior checks, hints, reference solution, reflection, extension and related navigation. Function exercises check returned behavior; early exercises check console output. Multiple implementations can pass those contracts.

The interface includes Start Here, a searchable module path, three learning modes, source editing/highlighting, real execution, captured diagnostics, supported snapshot replay, a visual-object library, HTML/CSS/JavaScript previews, live DOM/event/control inspection, a custom assertion laboratory, local API fixtures, complete project exports, progress records, a concept map and transparent recommendations. Passing current checks, learner explanations and independent transfer remain distinct.

Knowledge checks include output prediction, code reading, error identification, multiple selection, matching and written explanation. Written explanations are explicitly for learner/teacher review, not an automated semantic correctness claim.

Saving includes IndexedDB drafts, notes, bookmarks, preferences, attempts and saved experiments, with loading, duplication, renaming, deletion confirmations and versioned backup import/export. Imported check evidence is cleared until rerun. Optional practice goals count actual current passing records, not visits or streaks.

Help contains getting started, execution, console, editor, visual objects, exercises, testing, debugging, Build Studio, projects, saving, imports/exports, AI assistance, teaching, troubleshooting, FAQ, glossary, keyboard, accessibility and privacy. One consolidated programming guide replaces individual help icons. Presenter mode supplies full screen, readable code, notes, instruction navigation, reset and navigation/answer visibility controls.

## Deliberate scope limits

- The execution explorer replays supported instrumentation and authored trace points. It does not pause arbitrary JavaScript or inspect every internal call-stack or promise slot.
- Expression trees support a documented literal-expression subset. The practice module bundler supports prepared named imports, not a complete npm toolchain.
- Complex snapshots are bounded serialized views, not a complete native-object inspector; use explicit type/property checks for unusual nested values.
- Visual memory, scope, call-stack and event-loop diagrams are labeled educational views. Values and traces come from execution or explicitly identified local fixtures.
- DOM preview storage is a memory adapter. Exported storage behavior must be checked under the chosen hosting origin.
- Live external requests and live AI are not enabled. The core requires neither an account nor a key.
- This is a locally hostable, lazy-loaded site, not an installed service-worker/PWA cache. A local HTTP server can serve all supplied files without internet access.
- Demonstration timings are rehearsal estimates, not claims of produced videos. Printable HTML provides the scripts, worksheets and rubrics.

## Verification boundary

Automated execution, DOM and UI-model checks are supplied. Browser automation was unavailable in this session, so visual layouts, physical keyboard/screen-reader interaction, actual browser worker/iframe policy enforcement, fullscreen, print dialogs and browser download round-trips were not independently exercised here. They must be verified in the target browser after upload. See the precise test results in `TESTING.md`; do not infer a production accessibility or security certification.
