Code

Cover the worst-case attestation entry in the sandbox storage test

Custom MCP server add flow shows validation error

Instance upgrade fails during egress apply on agent staging

Agent does not react to or acknowledge Telegram stickers

Agent incorrectly claims live crypto market data is unavailable when querying multiple tokens

Agent exposes internal reasoning/planning instead of responding to user

Telegram routine runs successfully but message is not delivered on first execution

Agent does not recognize that conversation is already in Telegram

Agent cannot send generated files back as Telegram attachments

Long Telegram messages are split and partially missed by the agent

Telegram user message appears after agent starts working — conversation flow looks out of order

Telegram agent becomes completely stuck after receiving GIF or sticker

feat(llm): generic per-request thinking/effort control (provider-native mapping incl. DeepSeek chat_template_kwargs)

Multi-user access flow is broken — additional users get "Invalid secret" error

Telegram webhook is not activated after saving bot configuration

A voted attestation storage fee below the storage floor is neither rejected nor surfaced

Cloud.near.ai: allow staking path for Google/GitHub sign-ins

GitHub MCP extension startup gives confusing endpoint verification prompt instead of connecting

Memory: target-alias resolution is contract — move it to the domain layer

Guard the attestation sweep's gas budget against its scan limit

Feature: host-mediated IdentyClaw Passport (builtin.idcp + practitioner helper)

fix(turn-runner): retry_disposition() silent-redrive table is dead code — wire it or retire it

tracking(coding-tools): result_read 24 KiB preview ceiling + read-before-edit full-read gate (2000-line uneditable wall)

Epic: Pluggable agent loops — ACP executor, edge credential injection, kernel architecture

classify_delivery_outcome (MODEL delivery path) ignores Failed's vendor_message_refs, hiding partial-send evidence from the model — same gap #7475 fixes for notices

post_notice → release_connect_nudge collapses "delivered with no vendor ref" into "not delivered," letting a duplicate connect-nudge reach an already-nudged user

Epic: Make Reborn durable state profile-agnostic and migrate legacy profile roots

test(telegram): /model and /status lack end-to-end execution coverage — residue from #6733

hooks: deprecated with_hook_dispatcher seam — test it or delete the zero-caller methods — residue from #6945

extensions(packages): stale assets/<id> references + no package-anatomy gate — residue from #6492