Skip to content

Sync to nauro 1.2.0: lockstep pin + agent re-render#18

Merged
sronix merged 1 commit into
mainfrom
sync/nauro-1.2.0
Jul 2, 2026
Merged

Sync to nauro 1.2.0: lockstep pin + agent re-render#18
sronix merged 1 commit into
mainfrom
sync/nauro-1.2.0

Conversation

@sronix

@sronix sronix commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Why

nauro 1.2.0 is on PyPI; the plugin pins the CLI in lockstep and the committed agent copies drifted from the current render (the PR-description guidance moved to the three-core-section template upstream).

What changed

  • .claude-plugin/plugin.json version 1.1.0 -> 1.2.0.
  • Re-rendered agents/nauro-planner.md, agents/nauro-executor.md, agents/nauro-reviewer.md from the 1.2.0 source.
  • CHANGELOG entry for 1.2.0.

Test plan

nauro render-plugin . --check against the 1.2.0 source passes (rendered agents match the bundled source); CI runs the version-sync and byte-identity gates.

Pin plugin.json to nauro 1.2.0 and re-render the bundled planner,
executor, and reviewer agents, whose PR-description guidance moved to
the three-core-section template upstream. render-plugin --check passes
against the 1.2.0 source.
@sronix
sronix merged commit 89c1d38 into main Jul 2, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant