Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: clarify missing artifact failures

Browse Source
This commit is contained in:
Turtle
2026-08-12 15:41:53 +08:00
parent e6d2a97645
commit baf2bc6dc3
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.agents/notes/implemented/simplification/2026-08-12-separate-source-launch-from-build.md
View File

@@ -29,7 +29,7 @@ This decision owns build scheduling only. The [tsx ESM source-launch decision](.
## Consequences
- Repeated source launches do not wait for a complete repository build, and build output is not mixed with CLI output.
- Source users own artifact freshness. Missing artifacts fail loudly; existing stale frontend and client-plugin bundles can silently serve older browser code.
- Source users own artifact freshness. Missing artifacts stop startup, but only frontend and client-plugin failures direct users to `pnpm run build`; existing stale frontend and client-plugin bundles can silently serve older browser code.
- TUI, Web, and headless selection, argument forwarding, environment inheritance, and the tsx ESM launch vector remain unchanged.
- The root onboarding and CLI reference show build and launch as separate commands and document the stale-artifact behavior.