Zeus Dev Helper changelog

https://raw.githubusercontent.com/koten-ai/zeus_dev_helper_mcp/HEAD/AGENTS.md

− - No secrets in tool results, checklist evidence, the write-once sample creation logs (`beer-sample-build.md`, `travel-sample-build.md`, `yelp-demo-build.md`), or the support journals (`beer-sample-support.md`, `travel-sample-support.md`, `yelp-demo-support.md`)− Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|demo_yelp|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enable− Opt-in toolsets (`ZEUS_DEV_HELPER_TOOLSETS=core,lint,catalog` or `all`): catalog / lint / travel / support / handoff. Travel sample: `use_sample` (core) / `travel_golden_path` (travel toolset). The clone is https://github.com/koten-ai/demo_travel_sample.git. Start with `python -m travel_planner` on port 5000 unless `PORT` is set. The create path does not rewrite Docker files.+ - No secrets in tool results, checklist evidence, the write-once sample creation logs (`beer-sample-build.md`, `travel-sample-build.md`, `yelp-demo-build.md`), the support journals (`beer-sample-support.md`, `travel-sample-support.md`, `yelp-demo-support.md`), or the wish files (`beer-sample-wish.md`, `travel-sample-wish.md`, `yelp-demo-wish.md`). Passwords, bearer tokens, and API keys stay out of wish `what` and `why`.+ Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|demo_yelp|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enable+ Opt-in toolsets (`ZEUS_DEV_HELPER_TOOLSETS=core,lint,catalog` or `all`): catalog / lint / travel / support / handoff. Travel sample: `use_sample` (core) / `travel_golden_path` (travel toolset). The clone is https://github.com/koten-ai/demo_travel_sample.git. A named tag that exists is cloned exactly; an omitted version or a missing tag uses the latest semver tag; `main` is used only when that repository has no semver tags. The repository is tagged `0.1.0`. Start with `python -m travel_planner` o

version

0.7.12 → 0.7.13

version

0.7.11 → 0.7.12

https://raw.githubusercontent.com/koten-ai/zeus_dev_helper_mcp/HEAD/AGENTS.md

− Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|demo_yelp|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enable− Opt-in toolsets (`ZEUS_DEV_HELPER_TOOLSETS=core,lint,catalog` or `all`): catalog / lint / travel / support / handoff. Travel sample: `use_sample` (core) / `travel_golden_path` (travel toolset; set `DEMO_TRAVEL_SAMPLE_DIR` if cloned).− After 5.1+5.2 green: `recommend_data_plane_mcp`, `emit_mcp_config`, `handoff_to_multi` — **handoffs only** (handoff toolset).+ - Checklist **4.2** copies `bootstrap` `chat_request.contract` into the bound app `config.json` `zeus.scope_contracts`. `explain_scope` parses `bootstrap.chat_request` when `GET /v1/ai/chat_request.json` has no `## MINI-SCHEMA` heading. `bind_contract` with no path returns that snippet. A helper `chat_request.json` whose only field is `chat_request_dir` is a directory pointer, not an unstamped catalog. The Hub / Workbench note applies only when that live document has no real `contract.hash`. Pin+ - `verify_local_setup` imports `zeus_client` in this Helper process. The app `.venv` does not satisfy that check. Launch with `uvx --from 'zeus-dev-helper-mcp[agent]' zeus-dev-helper-mcp` (or `pip install 'zeus-dev-helper-mcp[agent]'` in that interpreter) and restart the MCP server. A Codex `:workspace` profile with network off reports pip `[Errno -2] Name or service not known` (`EAI_NONAME`). The app `requirements.txt` install stays a separate step from a process that has network.+ Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|demo_yelp|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enable+ Business rules: when the user asks to add or inject a business rule, call `inject_business_rules`. An omitted app uses the current directory when that directory is a Zeus app, otherwise the checklist sample (the beer app just created). `ask_user` means ask and wait, then call again with `app_dir` or `sample`. An explicit path that is not a Zeus app returns `not_a_zeus_app` and the message `app is not a Zeus enabled app`. The tool writes `config.json` `settings.rules` only. `wire_required` means + Opt-in toolsets (`ZEUS_DEV_HELPER_TOOLSETS=core,lint,catalog` or `all`): catalog / lint / travel / support / handoff. Travel sample: `use_sample` (core) / `travel_golden_path` (travel toolset). The clone is https://github.com/koten-ai/demo_travel_sample.git. Start with `python -m travel_planner` on port 5000 unless `PORT` is set. The create path does not rewrite Docker files.+ After 5.1+5.2 green: `recommend_data_plane_mcp`, `emit_mcp_config`, `handoff_to_multi` — **handoffs only** (handoff toolset). A one-scope sample, including beer and travel, does not take `handoff_to_multi` as the next build step. `handoff_to_multi` writes `jobs.host_url` only after the operator confirms two or more URLs, two or more scopes, or a report wait of 20 seconds to 5 minutes.

version

0.7.9 → 0.7.11

version

0.7.8 → 0.7.9

https://raw.githubusercontent.com/koten-ai/zeus_dev_helper_mcp/HEAD/AGENTS.md

− Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|demo_yelp|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enable+ Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|demo_yelp|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enable

https://raw.githubusercontent.com/koten-ai/zeus_dev_helper_mcp/HEAD/AGENTS.md

− - No secrets in tool results or checklist evidence+ - No secrets in tool results, checklist evidence, the write-once sample creation logs (`beer-sample-build.md`, `travel-sample-build.md`, `yelp-demo-build.md`), or the support journals (`beer-sample-support.md`, `travel-sample-support.md`, `yelp-demo-support.md`)

version

0.7.7 → 0.7.8

version

0.7.6 → 0.7.7

https://raw.githubusercontent.com/koten-ai/zeus_dev_helper_mcp/HEAD/AGENTS.md

− Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enabled toolset − Data-plane tools, Hub admin mutations, multi-agent jobs (ZJA). Integrating Zeus into an arbitrary existing application (use `demo_travel_sample` / `use_sample(sample=beer)` / `use_sample` instead).+ Default surface (`core`): `doctor` → (if user named URL/sample) `set_prereq` → `start_project` → `next_step` → `readiness_check` → `use_sample` | `scaffold_app` → `bind_contract` → `recommend_surface` → `smoke_test_zeus` / `smoke_test_agent` → `diagnose_error`. `start_project(sample=beer|travel|demo_yelp|api)` marks checklist 0.1 done. `next_step` then recommends `set_prereq` when no Zeus URL is stored, otherwise `readiness_check` then `use_sample` or `scaffold_app`, and only tools in the enable+ Data-plane tools, Hub admin mutations, multi-agent jobs (ZJA). Integrating Zeus into an arbitrary existing application (use `demo_travel_sample` / `use_sample(sample=beer)` / `use_sample(sample=demo_yelp)` / `use_sample` instead).

version

0.7.5 → 0.7.6