Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
Original file line number Diff line number Diff line change
Expand Up @@ -1004,7 +1004,7 @@ checks each edit (`BL-192`; merged `2474744`, PR #88).
run those commands without asking once the folder is trusted (`BL-206`;
merged `cefca6c`, PR #91). [#90](https://github.com/rabbilyasar/envshield/issues/90)
adds deployment and onboarding sections to `agent guide` (`BL-207`;
branch, not yet merged). The full order is
merged `6929753`, PR #92). The full order is
ROADMAP.md's "v5 — in progress". Nothing since `v4.9.1` is released.

**Previous phase (updated 2026-10-15): `v4.9.1` released; v5 V1 next.**
Expand Down
2 changes: 1 addition & 1 deletion BACKLOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2041,7 +2041,7 @@ Component: `core/agent_setup.py::install_hook_config` (`.claude/settings.json`)

### BL-207 — `agent guide` covers development only: nothing on deployment or onboarding

Type: `AI_AGENT` / `DOCUMENTATION` · Evidence: `CONFIRMED` (review of `agent_setup.guide()` while finishing #63, 2026-10-27) · Priority: **P2** · Status: **fixed by [#90](https://github.com/rabbilyasar/envshield/issues/90), branch `rabbilyasar/agent-guide-stages`, unmerged**
Type: `AI_AGENT` / `DOCUMENTATION` · Evidence: `CONFIRMED` (review of `agent_setup.guide()` while finishing #63, 2026-10-27) · Priority: **P2** · Status: **fixed by [#90](https://github.com/rabbilyasar/envshield/issues/90), merged `6929753` (PR #92), unreleased**
Component: `core/agent_setup.py::guide`

- **Current behavior:** the guide covers checking each edit and declaring new variables. For deployment it only says to set `requiredIn` and run the full check after editing a manifest. It doesn't say to add a variable required in an environment to that environment's manifest, how to check a manifest for an environment (`check --env E <manifest>`), or where `check --runtime` belongs in a deploy. For onboarding it only says not to run `setup` (it needs a terminal, #21). Nothing tells an agent helping a new developer to run `check --json` and relay each `by: "human"` step.
Expand Down
Loading