Repository navigation
Use release.settings.yml for canonical release settings #232
Description
Context and request
Contributors and agents need one consistent filename for optional repository release settings. The requested canonical path is .github/release.settings.yml, replacing .github/release.config.yml in current authoring guidance.
This is a separate delivery from current main at aa9b5cecc69f4cbe6aa04a5dd70ff9cdadeeac3d, which contains the completed MSXOrg/docs#209 / MSXOrg/docs#226 PR-record revision. A narrow open issue/PR search for both filenames found no matching canonical delivery to reuse. The independent MSXOrg/docs#196 and MSXOrg/docs#208 candidates are not this main-based delivery.
Acceptance criteria
- Current instructions, examples, evidence prompts, and links use only
.github/release.settings.ymlfor this optional canonical file; no current authoring guidance teaches the former filename or a fallback. - The
.githublocation, settings/schema keys, shared defaults, repository/caller precedence, omitted-input inheritance, optional-file behavior, target-route applicability, and required release-decision checks remain unchanged. - Release-range-first evidence, the complete PR-description example, its single shareable-summary boundary, conditional release metadata, Task/Bug planning, and repository-owned no-PR-template policy remain intact.
- No runtime loader, public input, publisher, artifact pipeline, release label, permission, pin, branch rule, or published historical record changes.
ConfigurationFile/.github/auto-release.ymlandSettingsPath/PSModule.ymlremain unchanged. - Focused checks demonstrate the former filename fails before the revision and the requested filename passes afterward. Existing documentation, Pester, index, link, lint, and site checks pass against the exact candidate head.
- One draft PR closes this Task; merging and GitHub auto-merge remain disabled.
Technical decisions
- The current tree has 17 active filename references in five pages:
src/docs/Ways-of-Working/PR-Format.md(2),src/docs/Ways-of-Working/Automation-Labels.md(1),src/docs/Capabilities/release-management/spec.md(3),src/docs/Capabilities/release-management/design.md(9), andsrc/docs/Capabilities/vscode-extension-framework/design.md(2). - Neither an actual
release.config.ymlnor arelease.settings.ymlfile exists in this checkout. These are documentation/protocol paths, not proof of an implemented runtime loader. Update the references only; do not create a settings file or implement a loader. - Extend the existing Pester documentation-contract suite,
tests/PR-Format.Tests.ps1, with bounded filename and unchanged-semantics checks. Preserve its existing PR-record and repository-policy checks. - A filename-only revision is the minimum complete option. Teaching both filenames or adding a legacy alias is rejected because no released compatibility boundary requiring one was found in this repository. If a real released loader/caller for the former filename is discovered, identify that boundary before choosing a migration.
- Preserve the merged documentation shape and all non-filename content. Historical/migration mentions are permitted only when clearly not current authoring guidance; no historical rewrite is part of this delivery.
- After pushing the immutable canonical source, share the exact five-page filename-only delta with the existing candidate owners so they can verify correspondence without copying unmerged scope or assuming automatic composition.
- Configure only this PR's supported native Agent merge maintenance (
address_reviews,fix_ci,resolve_conflictsenabled;merge_prdisabled). Do not use a state file, automation, or GitHub auto-merge workaround.
Implementation plan
- Add focused filename and preserved-semantics checks to
tests/PR-Format.Tests.ps1; demonstrate red on the unchanged source and verify the existing contract checks still pass. - Replace all 17 current filename references across the five owning pages, preserving every other setting and rule; confirm there is no actual file to rename.
- Run the focused green check, review the staged change, make small ordinary commits, push, and open the separate draft PR early.
- Enable only native PR maintenance with merging disabled, and read back the draft/auto-merge state.
- Run existing Pester, documentation-index, relative/cross-repository link, lint, and Zensical checks; review the complete exact-head diff and reconcile any accepted current-main changes before revalidation.
- Record standards alignment and the narrow issue-convergence result, publish the verified Task/PR, and report the immutable head, exact shared-page correspondence, and remaining human/CI gates.
Activity
MariusStorhaug commentedon Nov 1, 2026
Test-first evidence on main aa9b5ce: pinned Pester 6.0.1 ran 25 checks. All five new canonical-filename cases failed as intended; all 16 existing PR-record/repository-policy checks and four new unchanged-semantics checks passed. PSScriptAnalyzer reported no diagnostics. No documentation has changed yet.
MariusStorhaug commentedon Nov 1, 2026
All 17 canonical filename references are revised across the five owning pages. A baseline comparison proves each page equals main aa9b5ce with only release.config.yml replaced by release.settings.yml; every other setting, rule, and documentation shape is unchanged. The 25 focused checks now pass. Documentation indexes are current and relative links resolve across 127 pages. There is no real settings file or runtime loader to rename.
MariusStorhaug commentedon Nov 1, 2026
Draft MSXOrg/docs#233 is open at immutable head e65b9e0 with two ordinary commits. Native Agent merge is enabled only for address_reviews, fix_ci, and resolve_conflicts; merge_pr is false. REST read-back confirms draft=true, merged=false, and auto_merge=null. The complete Pester suite passes 89 tests, and the isolated repository-pinned Zensical 0.0.59 build succeeds. The automated review round is requested and running.
MariusStorhaug commentedon Nov 1, 2026
Exact-head validation is complete at e65b9e0 against unchanged current main aa9b5ce. All 89 local Pester tests, index/link/lint checks, and the pinned Zensical site build pass; the generated five HTML pages contain the same 17 requested references. All five required CI checks pass, and the exact-head automated review approves with zero comments. Both existing owners verified correspondence without importing this unmerged candidate: MSXOrg/docs#196 at ce9ca51 and MSXOrg/docs#208 at f68927e. Their retained default-bump/keyed-route and lifecycle schema/examples require sequential post-landing reconciliation, not automatic composition or restoration of older accepted content. No broader Task converges with this filename-only diff. Draft and merge-disabled holds remain.
MariusStorhaug commentedon Nov 1, 2026
The four new unchanged-semantics guards were also proven against isolated copies of the reviewed source and existing Pester suite: changing a release schema key, changing the shared patch default, making file absence opt a managed route out, and weakening required merge enforcement each produced exactly one intended assertion failure. Each baseline passed once and each restored fixture passed once. No reviewed source was modified, and all temporary fixtures, build output, and the isolated build environment were removed. Immutable head e65b9e0 remains clean and unchanged.
MariusStorhaug commentedon Nov 1, 2026
The verified Task and draft PR were published in the session and handed to the Project coordinator with immutable head e65b9e0, exact five-page correspondence, and remaining integration gates. All implementation-plan steps are complete. This Task remains open until human-reviewed integration; the PR remains draft, native maintenance remains non-merging, and GitHub auto-merge is disabled.