Native events, bounded rebuilds
pliego dev watches authored inputs through the operating system, debounces event bursts, ignores generated roots, and never follows source symlinks. A failed rebuild keeps the last verified site available while diagnostics remain live.
pliego dev 4400
pliego dev 4400 --lan
pliego dev 4400 --host 192.168.1.20Typed HMR decisions
- css
- Refresh the affected stylesheet URL without replacing the document
- content
- Fetch the rebuilt route after its verified artifact changes
- adapter
- Retire the owned adapter generation before loading its replacement
- reload
- Use a full document reload when the graph cannot prove a narrower action
HMR is derived from verified graph differences. It is an optimization of the development loop, never a second production runtime or an authority over unverified bytes.
Explain causality
pliego why artifact /
pliego why artifact assets/site.css
pliego why-rebuiltwhy artifact verifies the current receipt and pliego.graph.json before tracing source-to-route-to-artifact edges. why-rebuilt reads the latest bounded local development record and reports changed sources, invalidated routes, affected artifacts, byte changes, HMR choice, and receipt transition.
Failure preserves evidence
Compiler errors, invalid content, graph mismatches, and adapter build failures produce stable diagnostics without publishing a partial site. Correct the reported source and save again; the watcher retries from the last accepted generation.