agentlas 0.9.10 → 1.0.2

package/CHANGELOG.md

@@ -1,5 +1,92 @@
 # Changelog
 
+## 1.0.2 — 2026-07-27
+
+Workforce execution-contract fixes. Every worker in a `workforce` run now
+knows its exact execution authority, and the run recovers honestly instead
+of shipping broken output:
+
+- Tool-less (no-authority) workers are told explicitly that zero tools are
+  granted and that the deliverable must be authored directly in the reply.
+  Previously a borrowed worker was silently stripped of tools, tried to
+  call them anyway, leaked raw tool-call markup into deliverables, and
+  produced empty output on content-type tasks.
+- Worker handoffs are gated: leaked tool-call markup or an empty
+  deliverable triggers exactly one corrective re-run with a repair
+  directive; a repeat violation stops the run honestly with
+  `worker_output_contract_violation` (never a silent cleanup).
+- A verifier rejection now triggers exactly one corrective synthesis pass
+  with the verifier's issues attached, then a re-verification. A second
+  rejection still fails honestly (`workforce_verification_failed`), now
+  reporting both attempts' issues.
+- Selection handoff graphs are validated locally for circular
+  handsOffTo/reportsTo chains, so the structured repair loop fixes a cyclic
+  task force before the Hub sees it (previously a `task_force_cycle`
+  round-trip rejection).
+- Failure display: verifier/server `issues` arrays are printed line by line
+  instead of being truncated inside a capped JSON blob.
+
+## 1.0.1 — 2026-07-27
+
+- Fixes the two gates that failed on the v1.0.0 tag (never published):
+  project bootstrap no longer applies the context-map minimum-version gate
+  when probing Core capability — the real probe is
+  `agentlas_cloud/project_bootstrap.py`, and a source checkout without
+  version metadata (exactly what CI pins) was being filtered out, skipping
+  bootstrap entirely; and the smoke gate now asserts that `doctor` produces
+  a report rather than that the machine happens to have an agent CLI
+  installed (`doctor` still exits non-zero when it finds problems, which is
+  what scripts want).
+
+## 1.0.0 — 2026-07-27 (tagged, not published)
+
+- The 13,347-line v1 engine monolith is replaced by a modular v2 engine
+  (one concern per module: core/ runtimes/ agents/ sessions/ ui/ commands/
+  cloud/ hub/ mcp/ automation/ workforce/ storm/ experience/ project/
+  hephaestus/ oberon/ cloud-assets/). The full v1 command surface (56
+  commands, plus `uninstall` and `billing`) is live; nothing is stubbed and
+  there are no facades. The complete v1 engine remains recoverable at git
+  tag `legacy-v1-engine-snapshot`.
+- Multi-session subagent orchestration (Orca) is first-class: every run —
+  foreground chat, one-shot, storm/swarm worker, automation run — is a
+  session owned by one orchestrator. Subagent sessions persist as Desktop
+  division sub-chats (`kind='division'` + `parent_chat_id`). In the REPL:
+  `/spawn /sessions /tree /s /steer /kill /rm /broadcast`; typing during a
+  running turn queues steering on the resume session; ctrl-c interrupts the
+  turn. Background turn completions surface as one-line notices.
+- Cross-product contracts preserved and gated: shared Desktop SQLite schema
+  (user_version=45) and userData; runtime-doctor 3-product parity
+  (sync-runtime-doctor.sh PASS); experience taxonomy checksum;
+  desktop-terminal ontology loadout v2; portable Experience Bundle v1;
+  workforce ontology digests; mcp-child-launch env boundary; pinned
+  Agentlas OS Core harness. The known dev-only Hephaestus root defect and
+  the terminal-owned Desktop .app self-updater were removed (the latter
+  belongs to Desktop; `agentlas update` is npm-channel only).
+- Product-model parity with the current Desktop, not with v1: the Hub is
+  borrow-first, so `install` refuses call-only listings (bookmark or
+  `agentlas call`), instruction-less packages, trust grades below A/B, and
+  web-only agents, with Desktop's exact wording; `uninstall` mirrors
+  Desktop's firm-membership guard. Hub plugins register stdio servers
+  disabled and needing approval (the table is shared with Desktop, so an
+  auto-enabled row would have bypassed Desktop's own gate); remote MCP
+  endpoints must be https and a real `/mcp`|`/sse` path. Automation runs
+  execute in Desktop-identical hidden division sessions and skip
+  hub/browser/computer-use rows without consuming the lease or the
+  scheduled occurrence.
+- New-user protection: an unknown one-word argument is refused with an
+  edit-distance suggestion instead of being spent as a model call (a typo
+  used to start an agent and run shell); Desktop-only screen names
+  (site, trex, prompts, dashboard, marketplace, settings…) stop honestly;
+  invalid `--permission` values are refused before any model call instead
+  of being silently downgraded to read; `no_runtime` now prints the exact
+  CLI install commands.
+- Release validation pins Agentlas Core v1.1.67 commit
+  `04258b7541f604479dc04279146a506e363ad85e` (carried from 0.9.10).
+- smoke gate: 54 checks (surface, no-arg guards, fresh bootstrap, 30+
+  restored/new contract tests, runtime-doctor 3-product parity) — all
+  green. Verified end to end against a packed tarball installed with
+  `npm i -g` into a clean prefix and a pristine userData.
+
 ## 0.9.10 — 2026-07-26
 
 - `agentlas context refresh|refs|slice|impact|verify` now invokes the installed
@@ -12,6 +99,25 @@
   `04258b7541f604479dc04279146a506e363ad85e`, including Code Map v2 backlinks,
   functional Sitemap dependencies, and fail-closed impact verification.
 
+- Concurrent Terminal work against the Desktop-shared SQLite database now uses
+  one bounded lock policy. Every Terminal write transaction acquires writer
+  authority before reading mutable shared state, preventing deferred
+  read-to-write upgrades from failing with `database is locked` after a
+  provider already completed the user's work.
+- One-shot runs now honor the saved read/write boundary across run, firm,
+  Stormbreaker, swarm, build, Workforce, and context surfaces; an explicit
+  `--permission` remains a session-only override.
+- `agentlas context` invokes the compatible Agentlas Core context-map
+  capability directly and fails closed when it is unavailable. Older
+  Hephaestus launchers can no longer reinterpret `context verify` as a Hub
+  search. When multiple local Core installations coexist, Terminal now checks
+  bounded version metadata and skips an earlier runtime that cannot satisfy the
+  v1.1.66 context contract.
+- Scheduled automation output now renders only the model's final answer instead
+  of leaking Claude or Gemini stream-protocol JSON. The slash palette also
+  respects a real 40-column terminal while preserving arrow-key selection.
+- Top-level runtime failures follow the saved Terminal language, including
+  unknown runtime names and the no-runtime-available recovery message.
 ## 0.9.9 — 2026-07-26
 
 - In an explicitly initialized project, ordinary runs, firms, Stormbreaker, and