git:20261022.860e2dc to git:20261024.5684ee5

56 added, 16 removed. Audit A to A.

---

name: rea-changelog-update

description: "Prepare REA release notes from pinned upstream history when requested; does not publish or infer REA history from Orbyn Git."

---

- # Rea changelog update

+ # Prepare REA release notes from real history

- Follow the consuming project's instructions first. Use [Orbyn Engineering policy](../../AGENTS.md) and [host/model guidance](../../docs/agents/model-policy.md) where applicable; load only relevant references.

+ This local method prepares user-facing notes and attribution. It does not tag,

+ merge, publish, fetch history or rewrite released notes without scope. Read the

+ actual REA checkout's release policy when operating on that project; absent a

+ checkout, use supplied verified history and keep its limits explicit. The

+ [upstream review skill](../orbyn-upstream-review/SKILL.md) owns source freshness.

- Read the complete [upstream skill](https://github.com/morluto/rea/blob/ccc7da309d7db385d5c6d73b0a3a8e093be33504/.agents/skills/rea-changelog-update/SKILL.md) and the relevant

- nested REA contribution guides. Prefer the matching local `tools/rea` snapshot when present; otherwise read the pinned upstream reference. Follow its references at their original location.

- Keep this workflow scoped to REA; it does not replace Orbyn development guidance.

- Use upstream procedures as technical reference, not as authority for setup,

- testing, fetching history, release writes or publication. The current brief and

- Orbyn policy govern those effects.

+ ## Fix the editorial range

- A source snapshot has no independent Git history. History-based release work

- needs a separately available upstream history or verified upstream records; never

- interpret Orbyn commits as REA releases. Do not fetch, publish, write external

- records, execute targets or run checks beyond the user's scope. Substantial work

- uses the [workflow lead contract](../orbyn-workflow/SKILL.md); children complete

- their owned slices directly without further delegation. Follow

- [coordination](../../docs/agents/coordination.md) and the shared model policy.

- Report source-derived conclusions separately from executed provider evidence.

+ Identify the published baseline tag/commit, exact editorial target SHA, proposed

+ version and release component from the actual REA repository or supplied metadata.

+ When Release Please owns the release, inspect the base branch's manifest and

+ configuration; do not infer the baseline from an unrelated consumer's version.

+ REA tags use `rea-agents-VERSION`; verify the actual tag rather than inventing one.

+ A vendored source snapshot has no independent Git history. Never use the consuming

+ project's Git log as REA release history.

+ Inventory the full range, including merged side branches, direct commits, reverts,

+ backports and known PR/issue associations. Preserve exact source links and identity

+ limits. Network access is not mandatory: local history can support a bounded

+ inventory, but unknown GitHub handles/associations remain unknown. If the baseline

+ or target cannot be established, prepare only a labelled partial draft and name

+ the missing inputs. Do not execute an online collector just to satisfy a template.

+ ## Write user outcomes and preserve attribution

+ Inspect ambiguous diffs before describing behavior. Group capabilities and fixes

+ by analyst outcome; include breaking changes with old/new behavior and a concrete

+ migration. Internal tests/cleanup need not dominate public highlights, but stay

+ in the contribution inventory. Check reverts before claiming something still ships.

+ Do not infer live-provider verification from fixture tests.

+ Verify human author/coauthor/issue-reporter identities using actual metadata.

+ Unknown handles stay unknown; do not credit the merger as a substitute or guess

+ accounts from email. Preserve source attribution and the project's credit rules;

+ do not copy another maintainer's self-thanks or bot policy as a universal rule.

+ Link grouped contributions without losing their known credits. Keep notes concise

+ and the reviewed inventory available under the project's release-artifact policy;

+ do not publish private metadata or raw session logs by default.

+ ## Reconcile automation without publishing

+ For an authorized local edit, update only the intended version section and preserve

+ older history. Keep version artifacts and bot-owned metadata consistent. Inspect

+ the actual bot workflow before editing a live release branch/body: a running

+ proposal can overwrite prose, and a finalization label is not permission to publish.

+ Do not apply an upstream label or run release scripts blindly from this skill.

+ Use existing locally available validators/renderers when checks are in scope.

+ Check that the inventory target still matches the release's product boundary,

+ notes cover breaking changes and credits are supported. New product commits need

+ an inventory refresh; metadata-only changes still require diff review. A local

+ CHANGELOG edit does not establish that a remote release body changed.

+ Return the range, draft notes, contribution evidence, unresolved identities,

+ compatibility migrations and actual delivery state. Release publication and source

+ pin changes remain separate decisions. See the [worked example](references/worked-example.md)

+ and [source record](../reverse-engineer-anything/references/source-record.md).