main

Files	Last commit	Last update
agent-docs.generated.json	docs(release): fold the 0.10.3 staging entries into the dated release section The release heading is the top CHANGELOG section again, dated 2026-11-08, with the Runtime API agent discovery and provider-key check entries under Added and the website polish under Fixed. Regenerates crates/tui/CHANGELOG.md and web/data/agent-docs.generated.json. Verification: scripts/sync-changelog.sh; scripts/release/check-versions.sh --require-dated-release (version state OK); scripts/check-contributor-credit.py (15 contributors, all credited); cd web && npm run check (lint, tsc, build).	6 hours ago
features.generated.json	fix(app-server): gate file reverts on trust; repair the failures hosted CI surfaced The first hosted run on the mode-retirement candidate (c50612d6ab) failed in four jobs, none of them flaky. Lint and Parity: clippy's single_element_loop on two for mode in [AppMode::Agent] loops left behind by the Operate removal (plan_handoff.rs:151, codemode.rs:1604). Both are straight-line assertions now. Test (all three platforms): three app-server tests. - create_thread_..._named_permission_posture sent mode: "operate" and expected it echoed back. The runtime normalizes the retired spelling to Work, so it now asserts agent, which is the alias contract the release notes promise. - file_revert_route_validates_body_then_trust_then_ownership expected a 409 naming trusted mode for an untrusted thread and got the "restore point is unavailable" conflict instead, because the route had **no trust gate at all** — an untrusted thread that named a restore point it owned could rewrite workspace files. The gate now sits after body validation and before ownership, exactly the order its name describes, and refuses with the same wording the TUI's undo gate uses. - memory_workspace_scope_without_a_remote_is_a_client_error encoded the old "workspace scope needs an origin remote" contract that 3c7a43252ca deliberately replaced with a work-tree-path identity. It now asserts the scope resolves and is empty, which is what the code and the handler's own comment describe. Release candidate: "Verify exact candidate web surface" failed on [check-facts] FAIL — generated agent docs are stale. Re-ran npm run prebuild; agent-docs.generated.json and features.generated.json now match docs/features.toml and the current agent list. Verification: nextest codewhale-app-server -E on the three names → 3 passed; cargo fmt clean; sync-changelog --check clean. The trust gate is exercised only by the route test; no TUI or desktop journey touched it yet.	9 hours ago
latest-published-release.json	chore(web): record v0.10.2 as the published release Written by release.yml sync-release-record after v0.10.2 published. Gates run in the job: sync-latest-release --check, check-cloud-facts, check-facts.	15 days ago