STD-CHANGELOG-001: AI Changelog Standard

1. Scope & Purpose

This technical standard defines the automated, AI-generated Changelog Protocol across all Bluefly repositories and Gas City Rigs.

Aligned with STD-SEP-001 (Factory Operating OS vs Domain Separation): - BluCity-Packs (delivery/gitlab): Owns the reusable Formula (mol-gitlab-changelog-generate.toml) and Order (gitlab-merged-changelog.toml). - organization.refinery: Acts as the Release Convergence Authority responsible for executing the changelog turn upon MR merge. - Target File: CHANGELOG.md in root of every repository.

---

2. Formatting Specification (Keep a Changelog)

Every generated section MUST adhere to Keep a Changelog 1.1.0 and Conventional Commits:

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

### Added
- Feature description (!MR_IID)

### Fixed
- Bug fix description (!MR_IID)

### Security
- Security fix description (!MR_IID)

---

3. Automation Lifecycle

GitLab MR Merged to release/v0.1.x
          ↓
Gas City Event emitted (gitlab.mr_merged)
          ↓
Order triggered (gitlab-merged-changelog)
          ↓
Formula executed (mol-gitlab-changelog-generate)
          ↓
Refinery Agent synthesizes Keep-a-Changelog entry via prompt synth
          ↓
CHANGELOG.md committed & pushed to release/v0.1.x ([skip ci])