Elixir Agent Kit 1.2.2

Architecture review now checks who owns the field names, units and result shapes that cross a boundary, even when the call graph has no cycles. Functional refactoring distinguishes calculations from the data they return and preserves the timing of deferred reads. All 38 workflow IDs, installer behavior and dependencies are unchanged.

The evaluator also rejects duplicate execution records. See the controlled comparisons and their limits.

Install via the Git tag · Guia em português

Elixir Agent Kit 1.2.1

The installation guides in English and Portuguese, and the prompt for AI-assisted setup, now distinguish a Git tag from a published Hex package. To use this release today, pin the Git tag v1.2.1. This is a GitHub release only. The installer and all 38 workflows are unchanged.

Eight links from packaged documentation now open their versioned reports on GitHub. CI checks local Markdown file targets inside the built archive, including reports that would otherwise appear valid in a full checkout.

Verified with a fresh Mix project using the exact archive from an isolated, signed Hex registry: all 38 workflows installed, the lock checksum matched, production excluded the dependency, and uninstall preserved project instructions. Also verified installation from the public Git tag.

English setup · Instalação em português

Elixir Agent Kit 1.2.0

UI identity reviews now check which states a person sees together and whether the proposed next action is actually available. On a previously unseen handover screen, both guides identified the correct refusal; the new guide twice avoided assuming an unverified recovery destination. Blind comparison and limits.

Test strategy now checks whether an existing assertion already catches the regression. Seven other guides gained targeted corrections for stale commands, pipeline results, bundled checks, editable recovery, composed fields, clipped navigation, and reduced-motion end states. The field-round report links the cases and their limitations.

All 38 existing workflow IDs, configuration keys, installer behavior and dependencies are preserved. No Cyclops dependency. Install from the Git tag following the versioned guide. This is a GitHub release only.

Elixir Agent Kit 1.1.0

Code reviews can now prioritize a failure scenario using a changed branch, caller, or previous fix; small reviews skip this step. Architecture review clarifies what Mix xref cycles do and do not establish. Neither workflow requires Cyclops.

The architecture pilot is closed: with a single catalog and working adapter, the real fix cut a warm comment-only rebuild from 45 to 26 source files. This is a source-count result, not a timing benchmark. Read the evaluation.

To upgrade, pin tag: "v1.1.0", run mix deps.update elixir_agent_kit, preview with mix agent_kit.sync --dry-run, then run mix agent_kit.sync, mix agent_kit.check and your project gates. Same workflow IDs and installer. This is a Git release.

Elixir Agent Kit 1.0.0

First stable release of the Git dependency. Ships 38 workflows, size-guided routing, migration checks and a dependency-free installer. Verified on Elixir 1.15.8/OTP 26.2 and Elixir 1.20.5/OTP 29.1.2. This is a GitHub release, not a Hex publication.

Elixir Agent Kit 0.10.0

• Quality review of all 38 workflows: every numbered step now ends in an
  observable "Done when" (revision-lineage, provider-calls, responsive-layout,
  accessibility, motion-design, test-strategy, async-state and process-lifecycle
  gained theirs), check_library.py flags the obsolete mix xref callers and
  Repo.transaction in workflow bodies, and data-contracts uses Repo.transact/2.
• Trigger and separating-rule fixes: architecture-review names
  functional-refactoring and readable-code and stresses ownership over
  duplication; accessibility carves out one control's keyboard path and
  separates WCAG target size from width and reach; revision-lineage carves out
  stale asynchronous results. Mechanics that drift are pointed at the elixir/
  references instead of restated, and navigation-ux and performance stop and
  ask before a schema change.

Elixir Agent Kit 0.9.0

• Task size now changes the route and the execution: ROUTING.md gains a "Size
  changes the choice" section, every workflow gains a required ## Size section
  saying what to trim, keep or slice at each size, and START.md surfaces the
  rule at choice time. scripts/check_library.py requires the section and its
  Small, Medium and Large bullets in all 38 workflows.

• Five new evaluation cases E83 to E87 (87 total) test size-routed pairs: the
  same kind of request changes route by size (competing flows, paid calls), and a
  fully specified small edit stays NONE.

• docs/versioning.md defines the public interface under semantic versioning
  (configuration keys, Mix tasks and flags, file layout, the state.tsv format,
  the block markers and the stable workflow IDs), the versioning and deprecation
  policy, and an upgrade guide; scripts/check_library.py keeps the documented
  workflow IDs in sync with catalog.tsv.

• Every code and backend workflow has a medium and a large evaluation case
  (E67 to E82, 82 total), and scripts/check_library.py enforces that coverage.

• scripts/eval_matrix.py prints the coverage matrix by workflow and task size,
  and, from live-round result files in evals/results/*.tsv, an outcome matrix of
  routing, stated size, the plan rule and completion. It reads files only and
  calls no model; check_library.py validates every committed result file.

• evals/README.md documents how to run a size round.

v0.8.0

• New workflows functional-refactoring and readable-code (code area), both
  behavior-preserving and analyze-and-fix. functional-refactoring makes a
  module's hidden inputs explicit at the edge, extracts its decisions as pure
  functions tested without stubs and layers its functions (ideas from Grokking
  Simplicity, concept only). readable-code resolves reading obstacles inside
  working code (names, nesting, comments, error flow) through the code-shape
  vocabulary (ideas from Clean Code, concept only).
• ROUTING.md routes refactoring requests by symptom; a vague request with both
  symptoms runs functional-refactoring first and readable-code as a later
  slice. abstraction-layers, module-design, code-consolidation and
  house-patterns name the new boundaries.
• Evaluation cases E63 to E66 (66 total).

v0.6.0

• The routing guide separates the pairs live sessions confused: density within one
  width versus behavior across widths, code review versus delivery validation,
  notification transport versus alert lifecycle, a late result on the wrong revision
  versus a stale result overwriting state, and debugging as the fallback when no
  area workflow names the symptom. async-state names a failed refresh that erases
  the last good state. The catalog header lists all eight operational domains, and
  the installer history left the practice-evolution guide.
• Evaluation cases: E05 expects responsive-layout, E07 expects debugging, and
  E47 to E50 add a phone overflow, a backend NONE, a density-only screen and a
  measured render time, so every workflow has a primary case.
• scripts/check_library.py now enforces the workflow template (headings in order,
  a When to use that goes beyond the catalog sentence, Start at and Minimum
  lines, no em dashes or operator tools), a primary routing case per workflow,
  CATALOG.md and README rows equal to catalog.tsv, the evals README case count,
  Markdown anchors, external skill links pinned to a commit, and every documented
  tag equal to the mix.exs version.
• Every workflow now opens with concrete symptoms and the linked neighbors it hands
  off to, orders its inputs with a Start at line, ends each step in a condition,
  names the artifact its first step produces, and marks the single Minimum
  evidence that proves the fix, so a session that names a workflow has something
  to open first and a bound to stop at. The 26 workflows that still repeated their
  catalog sentence are rewritten to the depth of the eight revised earlier; those
  eight gain the same Start at and Minimum markers. layout-density no longer
  claims width behavior, which belongs to responsive-layout.
• The managed block is found and hashed from marker to marker, so a linter that
  removes the blank lines around it, a CRLF checkout or a stripped final newline no
  longer reports "malformed" markers; blocks keep the file's line endings and owned
  files converted to CRLF are not drift. Blocks recorded by earlier versions are
  still recognized on upgrade.
• Generated AGENTS.md and CLAUDE.md start at the first line, and a block is
  appended after exactly one blank line.
• A CLAUDE.md that already imports AGENTS.md is not given a second @AGENTS.md.
• START.md step 4 asks for the workflow's Start at input as the first file opened
  and the artifact its first step produces, so a named workflow is also a read one.
• A declared :elixir_agent_kit entry in mix.exs is the source of truth; keys
  removed there fall back to defaults instead of the recorded state.
• install, sync and check fail when the dependency's library is incomplete at
  the path the links point at; uninstall refuses selection flags; the tasks print a
  note when CLAUDE.md exists without :claude selected; outdated times out
  instead of hanging on a stalled network. Task docs describe each task's own flags.
• docs/README.pt-BR.md mirrors README.md section by section.
• mix.exs carries a docs: configuration for maintainers who add ex_doc to a
  local checkout; the package itself still declares no dependency, because a nested
  dev dependency would be fetched by every consumer. Publish with
  mix hex.publish package.
• CI lints scripts/ with pyflakes.

v0.5.3

• Move the selection to the start of the session: the generated block, START.md and
  the pointer skills now say "before opening any source file for a change or a review,
  select one workflow and name it, or NONE", and step 4 ends with "then open the code
  and investigate the way the workflow says". The v0.5.2 remeasure showed sessions
  reading the local contract and investigating for 50 to 100 turns before the kit,
  then hitting their cap on START.md. Existing installations pick it up on sync.