// engine/universal-rules/rules/planu-release-policy.ts — Universal rule: release decision
function buildBody() {
    return `# Planu Release Policy

Auto-generated by \`init_project\`. Do not edit manually.

## Rule

When implementation changes are complete and validated, always address release explicitly:

- create the release when the user has already requested shipping or publishing
- otherwise ask before publishing, tagging, or pushing externally visible release artifacts

## Required Release Checklist

- tests and validation commands passed
- changelog or release notes updated when applicable
- package version and git tag stay aligned
- main/develop branch state is reconciled when the repository uses both
- published package smoke check is run after release when applicable

## Hard Blocks

- Do not silently skip release discussion after completed product/runtime changes.
- Do not publish without validation evidence.
- Do not leave release notes promising capabilities that are not in the public runtime.
`;
}
export const planuReleasePolicyRule = {
    id: 'planu-release-policy',
    name: 'Planu Release Policy',
    description: 'Requires an explicit release decision after validated implementation work.',
    category: 'safety',
    applicableHosts: ['all'],
    defaultEnabled: true,
    buildContent: (_host) => buildBody(),
};
//# sourceMappingURL=planu-release-policy.js.map