Files
open-design/shells/AGENTS.md
d03bf69d58 feat(standalone): complete Terminal exact lifecycle (#7319)
* feat(standalone): bootstrap terminal exact lifecycle

* feat(standalone): complete terminal exact lifecycle

* fix(ci): build standalone during postinstall

* fix(standalone): repair exact lifecycle recovery

Generated-By: looper 0.11.2 (runner=fixer, agent=codex)

* fix(standalone): make exact updates replay-safe

Generated-By: looper 0.11.2 (runner=fixer, agent=codex)

* fix(terminal): enforce replay-safe exact carrier

Generated-By: looper 0.11.2 (runner=fixer, agent=codex)

* fix(standalone): align active update replay state

Generated-By: looper 0.11.2 (runner=fixer, agent=codex)

* fix(standalone): preserve exact channel lifecycle

Generated-By: looper 0.11.2 (runner=fixer, agent=codex)

---------

Co-authored-by: Looper <looper@noreply.github.com>
2026-08-25 03:56:31 +00:00

14 lines
744 B
Markdown

# Shell guide
Follow the root `AGENTS.md` first. Shells are product carriers and user-entry adapters. They may depend on public package contracts, but must not import app-private source or redefine distribution and generation semantics.
## Active shells
- `shells/terminal`: exact official Node carrier and terminal lifecycle entrypoint. It owns shell identity, repository configuration, and CLI presentation. `packages/standalone` owns verification and state transitions; `apps/closure` owns Closure content.
## Boundary rules
- A shell must not import `apps/**`.
- Shell-specific environment variables, workflow contexts, and storage credentials must not enter package contracts.
- Tests live in `shells/<name>/tests`, sibling to `src`.