[immakermatty]

Status: ready for review. Plan: HumanAndMachine-ai Mission Control DEV-6626. This brings Lazurio/composio#3 into Environments.

Why

In Matěj's onboarding session and in the end-to-end test of 2026-10-19 (#507 item 8), the Composio dialog noticed an Authorize up to about a minute late. The cause was in the Composio CLI: composio login --poll backed off exponentially, with checks at about 0, 5, 10, 15, 20, 25, 35, 54, 92 and 169 s. Lazurio's fork fixed it in Lazurio/composio#3 (one check every 5 s for up to 10 minutes), and Matěj authorized the release. @composio/cli@0.4.3-lazurio.2 is published from commit e52fc87.

What changes

• src/tools/composio-build.ts:
  • version 0.4.3-lazurio.2;
  • installer commit e52fc87e7eaf07b7d83e0b50a8dd0c392d215294, the release's own commit. Its install.sh blob 68918632… is identical to 107730453's;
  • the four archive SHA-256 values, checked against the release's checksums.txt and re-hashed from the downloaded zips;
  • the header comment lists the third change.
• The agents' instructions (src/tools/catalog.ts) say "three changes".
• Integrace's update line (src/integrations/model.ts): an Environment on 0.4.3-lazurio.1 is no longer the pinned build. Without this, Apps → Integrace would say "Aktualizujte Composio, ať tu můžete účty odpojovat a vidět jejich jména." and lazurio integrations list would tell agents accounts cannot be disconnected. Both are false: lazurio.1 already removes without a prompt and names accounts. composio.update is now also false where the CLI already disconnects. Settings → Tools still offers the update ("Toto není sestavení, které Lazurio používá (0.4.3-lazurio.2).").
• Docs: docs/decisions.md gets an F42 note of 2026-10-19 (the records of 2026-10-13 are unchanged). docs/integrations.md, docs/environment-tools.md and docs/launchpad-development.md state the new pin.

Rollout

An Environment on lazurio.1 sees the amber note in Settings → Tools with Update. lazurio tools update composio moves it to lazurio.2 and keeps the sign-in. The curated installation installs lazurio.2 directly.

Verification

• Tests for the update from lazurio.1 and from an older build, the amber note, the update route, and the Integrace line beside an earlier Lazurio build. They fail without the change.
• Focused tests: 113 pass across 6 files (re-run by the reviewer agent). tsc --noEmit, lint and check:public are clean.
• Full bun test: 4224 pass, 9 skip, 2 fail, at load average about 41. Both failures are timing in untouched files: organization-module-create passes alone, and cli.test.ts "previews explicit fixture" passes with --timeout 30000.
• The fork's release workflow installed the build on Linux and macOS and printed composio --version: 0.4.3-lazurio.2.

🤖 Generated with Claude Code

[agentrozjedemeai]

@immakermatty Exact-head review of e522bb8 (base b3fc3ba): approved. The 0.4.3-lazurio.2 release tag resolves to e52fc87; its install.sh Git blob (68918632a812715605dbbeced66fcd824fcd0b9f) matches 107730453, and all four pinned archive SHA-256 values match the release checksums.txt and published asset digests. The lazurio.1 scenario keeps Integrace quiet when disconnect is available while Settings → Tools still offers Update; the fixture update preserves sign-in. Local isolated checkout: 132 focused tests pass (6 files), check:static passes (lint, typecheck, check:public, build and smoke), git diff --check clean. Exact-head GitHub CI is green; no unresolved review threads. No merge, release or deployment performed.