0d1a2102eb
Playground archived at branch archive/playground-solidjs (tag playground-solidjs-final) and deleted from main. Retargets: - run-all-tests.sh stage 5 → manifold (typecheck + bun test + build + playwright via non-snap node runner, BUILD-PLAN gotcha) - ci.yml playground-tests → manifold-tests; osc-bridge.yml → manifold/osc-bridge (was already broken: playground/osc-bridge no longer existed) - codegen: TS emission target removed (returns at P5 → manifold); golden test now C++-only; TS emitters retained dormant - .gitignore: manifold/osc-bridge paths; drop dead playground faust exception - docs: AGENTS.md gates, README quickstart, MAP.md, ALIGNMENT.md (C15 now archive-only — defect #1 updated), AGENT-REFERENCE.md, specs/MAIN.md Part of docs/specs/plans/one-core-engine-refactor.md P1.
31 lines
1.4 KiB
Markdown
31 lines
1.4 KiB
Markdown
# Agent Instructions — MEMLNaut-NISPS
|
|
|
|
One C++20 NISPS core targets RP2350 firmware and the Manifold React/WASM browser app. Read
|
|
`MAP.md`, `ALIGNMENT.md`, and `docs/AGENT-REFERENCE.md`; for Manifold UI work read
|
|
`manifold/ONBOARDING.md` first. Parameter JSON schemas generate the C++ contracts
|
|
(TS codegen returns at P5 of `docs/specs/plans/one-core-engine-refactor.md`).
|
|
|
|
## Gates
|
|
|
|
```bash
|
|
bash scripts/build-cpp-tests.sh
|
|
bash scripts/parity-check.sh
|
|
bash scripts/lint-cpp.sh
|
|
scripts/build-firmware.sh [VARIANT]
|
|
cd manifold && bun run typecheck && bun run test && bun run build
|
|
```
|
|
|
|
- `nisps/` must remain platform-neutral and allocation-free in hot paths: no heap, no
|
|
virtual dispatch, `.f` float literals, deterministic per-instance RNG, and the memory/
|
|
hot-path attributes from `nisps/core/perf.hpp`.
|
|
- Firmware and WASM use the same engines/modes. Cross-platform outputs must retain parity;
|
|
do not patch target-specific behavior around a core mismatch.
|
|
- Schema changes require codegen and both generated-language outputs in the same change.
|
|
- Audio-thread/WASM-worklet communication stays bounded and real-time safe.
|
|
- Preserve dual-core firmware ownership and SPSC synchronization; UI/control work must not
|
|
block the audio path.
|
|
- UI behavior changes need the targeted unit/E2E evidence and the verification chokepoints
|
|
documented in the detailed reference.
|
|
|
|
Use `ergo` for coding tasks. Keep `MAP.md`, `ALIGNMENT.md`, and affected docs synchronized
|
|
with code.
|