[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

tau@1.2.0

Minor Changes

• #656
  24e14d6 Thanks
  @sQVe! - Carry planned journeys into slice tickets and assign each
  journey item to one agent ticket for its journey file, test, and QA guide index row. Keep only
  built steps in journey files and tests. The slice that delivers the last step depends on the
  earlier steps and checks that the whole journey passes.

• #646
  5e9305f Thanks
  @sQVe! - Name the repository's QA guide in every qa worker brief. A
  qa launch adds QA guide: read .pi/qa.md when the worktree has that file, and says there is no
  QA guide when it does not. The line also appears when the repository has no qa.repositories
  entry. The manager reads the guide and assigns the sections that a change needs.

• #652
  1da6f18 Thanks
  @sQVe! - Add a QA guide template and make the manager and the qa
  worker follow its parts. With a guide, the manager does the steps under "The manager starts" for
  the assigned sections, puts the lines the guide asks for in the brief, and stops what it started
  when every worker that uses it has reported, or when the launch fails. It launches no qa worker
  when only "Not testable" applies. The qa worker runs a section's "Reach it" proof first and asks
  the parent when it fails.

• #653
  e051f8e Thanks
  @sQVe! - Add an optional journey index to the QA guide template, with
  separate journey files for repeatable user flows. The manager assigns journeys that the change
  touches. The qa worker reads each assigned file, walks its steps in order, and compares visible
  results and the end state.

• #658
  c295f79 Thanks
  @sQVe! - Let pr evidence select the saved review chain and return
  its coverage. It no longer takes chain; use review to choose a chain when several candidates
  match. The pr and finish-slice skills use the returned chain instead of selecting and building
  one themselves.

Patch Changes

• #661
  50b3584 Thanks
  @sQVe! - Run slice QA before the acceptance audit. Refresh affected
  audit rows after PR checks and use their current evidence for the draft suggestion and preview.

• #664
  efdd71f Thanks
  @sQVe! - Shorten the code_review, pr, pr_feedback, stack, draft_review,
  and slice tool descriptions. Reduce the measured manager prompt from 58,445 to 49,705 characters.
  No tool or behavior changed.

• #650
  140d77c Thanks
  @sQVe! - The Merge when green snippet now tells the session to report
  the merge result and then close its space. The space stays open when the PR did not merge.

• #662
  b6da958 Thanks
  @sQVe! - Name reviews "first" or "fix" in skills. Define section,
  recipe, and journey in the QA guide template.

• #659
  d8ae5f1 Thanks
  @sQVe! - Add pnpm pi-session, which runs one headless Pi session that
  loads a Tau checkout, sends one prompt, waits for the workers it launched, and saves the event
  log. The finish-slice skill now tells the manager to run each manual check itself and never hand
  it to the user.

• #660
  d030195 Thanks
  @sQVe! - Change two parts of the QA guide template so a reader can
  follow them. Under "The manager starts", the template now shows one bullet per section with three
  labeled lines, Start, Check that it is up, and Stop, instead of a table. Under "Choose sections",
  the list of changes that need no qa launch now has its own lead-in line, "No launch, and unclear
  impact:".

• #655
  0c44369 Thanks
  @sQVe! - Report a result for every QA journey step and the end state:
  as written, differs, skipped, or blocked. Never report a journey as passed when a step did not
  run. Aim for at most eight journeys per product, without requiring a minimum.

• #654
  19a0aef Thanks
  @sQVe! - Share QA launch and reuse rules across manager guidance and
  pull requests, and keep review timing and fix round rules in one place.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: sQVe/tau
• Branch: main
• File: .coderabbit.yaml
• Commit: efdd71f
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 8d637021-be22-4f64-b42e-14d3ad035e81

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn