Verify a change to Sema's LLM/agent layer (sema-llm) using the two-tier flow that's caught real bugs (see CHANGELOG 1.21.x). $ARGUMENTS names the feature(s) to focus on (e.g. "tool loop", "fallback", "caching", "reasoning-effort"); if empty, cover the agent loop, fallback, cache, and budget.
Run the Sema release procedure end-to-end. $ARGUMENTS may contain the target version (e.g. 1.21.2) or a bump kind (patch/minor/major); if absent, infer the bump from the unreleased changes and confirm before tagging.
You are orchestrating a multi-agent consensus analysis. You automatically select the right mix of PL designer personas and Sema-specific technical roles based on the problem type.
You are orchestrating a multi-agent consensus analysis using the perspectives of real programming language designers. Each agent argues from that person's documented philosophy — not a generic lens.
You are orchestrating a multi-agent consensus analysis using domain-specific roles tailored to the Sema project. Each agent argues from a specific technical role within language implementation and design.
You are orchestrating a multi-agent consensus analysis. Your job is to spawn N independent agents, collect their responses, and synthesize consensus/divergence/outliers.