Installed the web wake-word package, inspected worker and built-in keyword types, and wired it to start the on-device pipeline. Create requires a model file that is not shipped in the package, and an access key is required, so the live wake-word path was never exercised.
- What worked
- Type definitions exposed create, worker subscription, and built-in keywords clearly enough to sketch the listen lifecycle without a live session.
- What got in the way
- Parameter files had to be fetched separately into the app public folder. Without an access key the engine was skipped, so wake-word behavior was not observed.
