[polewskm]

Bumps NCode Review to v1.0.0 (d14405f82771819586a5ccbff636929dc894b780), the first full release, which freezes the caller–engine interface. This repository's caller still pins v0.3.1.

• Adds closed to the pull_request_target types. When a pull request closes, a separate outcomes job records each finding's outcome (fixed, dismissed, acknowledged or ignored) in the summary comment, by rules alone. That job runs outside the code-review environment, without id-token: write, the Bedrock key or a checkout. v0.3.1 treated a closed pull request like an opened one, so closed waited for this pin.
• The review job gets v0.4.0's and v1.0.0's caller changes: /review explain and /review teach each run in a concurrency group of their own, and issues: read lets the bot link a finding to an open issue that already tracks it.
• v1.0.0 runs verification by default and has every engine change since v0.3.1 (changelog).

The file is now the caller in NCode Review's README and in NCodeGroup/code-review's own workflow.

Refs NCodeGroup/code-review#97

[ncode-review]

🤖 NCode Review at 22da372: 2 new findings on the changed lines.

[ncode-review]

🤖 Review complete

Verdict: ✅ Approve — No findings.

5 reviewers run — 0 findings (run details)

Reviewer	Model	Findings	Top
conventions	sonnet-5-5	0	🟢
correctness	sonnet-5-5	0	🟢
hygiene	haiku-5-5	0	🟢
rule-check	sonnet-5-5	0	🟢
security	sonnet-5-5	0	🟢

Skipped: api-compat, architecture, completeness, data-model, infrastructure, intent, performance, tests

_{Trial: findings are posted as review threads and in the check run. $0.17 on Amazon Bedrock, 31s, at acc3c47. (how to interact)}

📋 Outcomes

Merged at acc3c47: 3 fixed, 1 dismissed, 0 acknowledged, 0 ignored.

Finding	Reviewer	Severity	Outcome
F1 at 22da372	rule-check	🟠 Should fix	👎 dismissed
F2 at 22da372	hygiene	🟡 Nit	✅ fixed
F1 at 9c56218	rule-check	🟡 Nit	✅ fixed
F2 at 9c56218	hygiene	🟡 Nit	✅ fixed

[polewskm]

/review

[ncode-review]

🤖 NCode Review at 9c56218: 2 new findings on the changed lines.

[polewskm]

/review