Repository navigation
Description
Outcome
Repository and workflow maintainers can adopt the existing release-settings contract at .github\release.settings.yml without silently losing policy from the former conventional file. This leaf extracts only the already-implemented filename migration from #109; it adds no release functionality.
Acceptance criteria
- The
SettingsFilePathinput supplied by Task111 preserves explicit custom-path control. This filename layer changes only its conventional default to.github\release.settings.yml; the publicConfigurationFile->SettingsFilePathrename belongs to Task111/PR109. - Valid new-default settings load when the input is omitted; intentional absence retains valid existing defaults and invocation inputs.
- The removed
.github\auto-release.ymlpath is not a fallback or alias. Legacy-only settings, conflicting files, and explicit selections of that path fail before GitHub-Script starts. The diagnostic names the selected path and the compatible action update. - Deliberate existing custom paths remain supported. A missing selected path cannot silently discard existing legacy conventional policy.
- The filename layer inherits the shared schema and startup resolver from Resolve releases from owned labels and effective settings #111. All 16 settings support file values and matching nonempty named overrides. Omitted or empty inputs keep file values. Explicit false remains an override. The file selector remains separate, and the filename layer does not add a second resolver.
- Relative selectors and the old-file guard use the initial directory: an explicit
WorkingDirectoryinput, otherwisegithub.workspace. File-defined execution directories resolve from the workspace after file selection. They do not select another file or move the old-file check. - The layer contains its actual reader change, behavioral cases, target-state README and complete coordinated filename/reference/caller adoption record.
- The original extraction recovers the preserved accepted source exactly. Later resolver revisions remain inherited. The guard moves from
main.ps1toInitialize-ReleaseConfiguration.ps1so it runs before startup. Only four filename-specific paths differ from the updated resolver.
Technical decisions
The preserved original is 03e20b8293dd8dfb41bead3255930a5edbb2e9bb (tree b2eb47c43236917ba6bc489a9fea391a66f79709). Its historical filename slice changes action.yml, src/main.ps1, tests/Release-GHRepository.Tests.ps1, and README.md. The startup revision moves the reader guard to src\Initialize-ReleaseConfiguration.ps1. The resolver remains owned by #111. This draft targets that resolver branch and uses its real bootstrap and settings handoff. The native dependency remains unchanged.
Canonical naming and reader/migration guidance is verified at MSXOrg/docs d5bc395416fb4194c1801871990f46faf301bf8a, including Naming#solution-settings-files, PR Format, Release Management settings and Consumer Upgrades. A documented native producer path is distinct from a naming convention. This extraction does not migrate production callers or module settings.
Implementation plan
- Pin and preserve original source, live PR and existing accepted behavior before splitting.
- Create the layer in its own isolated owning worktree from the committed/pushed resolver layer.
- Restore only the four original filename blobs in one ordinary additive commit; keep all new-input/resolver/publication scope out of the layer delta.
- Run existing controlled tests/analysis at both isolated heads; prove the cumulative top tree equals original
03e20b8and the layer patch equals the accepted filename delta. - Open a separate draft PR against the immediate resolver base and record its actual Task/base/head, adoption path and source-preservation proof.
- Verify new-head CI/review evidence or state exact pending/unavailable evidence; retain draft and no automatic merge.
Uniform startup settings revision
The user selected one configurable interface for all meaningful settings. #109 now resolves all 16 settings before GitHub-Script starts. One private metadata schema supplies type, default, and startup or release phase. The standard VersionPrefix remains v, and custom prefixes remain supported.
Lower source 7ab87bc07d58a513716e50c947d76852fc6065e9 is inherited through merge 518264270d75170d0eed6f283d4942ec31adb480. Its validated workflow-only follow-up 1040867819d77ef79c88d4492e10e8a8a7b6a37b is inherited through final merge a2921454e8ebaefc01e3cd8c2b6adff10a592a42, tree 5bcff6d2bf113e5d9880b84e0d4de52d2206ddba. The final upper differs in README.md, action.yml, src\Initialize-ReleaseConfiguration.ps1, and tests\Release-GHRepository.Tests.ps1: 302 insertions and 6 deletions. The controller, helper module, and workflows match the final lower source.
Two new bootstrap regression cases failed before the guard moved and passed after it. They prove that legacy-only and conflicting conventional files fail before a startup output handoff. Two other cases prove that default-file selection and startup settings use the initial directory without execution-directory rediscovery.
All 245 repository cases pass at the final upper source, with zero failures, skips, or not-run cases. PSScriptAnalyzer 1.25.0 reports no diagnostics in five PowerShell files. README Markdown lint passes. The final-head action run passes, including all 245 cases and both real caller invocations. File-defined startup fields reach GitHub-Script, then named false and workspace overrides win. Fixture preparation and cleanup also pass.
All final-head lint contexts, actions analysis, and CodeQL pass. The final-head review is approved with no open issues. This is automated review, not human approval or publication authority. Three real-version-library controls also confirm safe cleanup with standard and version-like prefixes.
The lower configuration work and its metadata are complete at 1040867819d77ef79c88d4492e10e8a8a7b6a37b. Its review is commented, not approved. The reviewer resolved the Ubuntu path claim after actual default-file reads showed the correct physical path. Two lower findings remain open: publication checkout source and label mutation before the non-PR guard. This configuration correction does not change those authority controls. These findings and the native prerequisite remain explicit readiness limits.
The old candidate counts and review results below are historical evidence, not approval of this startup revision. Both PRs remain in draft. The upper has no release labels, and neither source check authorizes publication.
Boundaries
No amend, force-push, reset, history deletion, original PR closure, unrelated issue closure, Template-Action change, inherited prerelease-counter fix, historical note repair, Process edits, new publisher authority, settings/ruleset/permission change, merge, or version/tag/release/publication. Existing #108 and #112 remain separately owned. The original resolver prerequisite and all genuine review/production limits remain. This is an unpublished development layer, never a production dependency.
Named-input prerequisite revision
The subsequent user-directed interface revision belongs to Task111/PR109. Its pushed source is 47202d7c2f350ae67fda2d5d9e328be3b0d3d492, tree bd6bc0933bef0cf974249b565f621ad4f525a030. It removes the unpublished structured CallerOverrides proposal and uses the existing named settings with an exact inherit input default. The shared effective defaults stay centralized in action.yml. Explicit named inputs override repository settings, including false and supported empty strings; invalid repository values still fail before publication.
The original exact source proof remains valid for historical extraction head 905ced93d13306c18ddf239d8bc2a02b4b48533a; it is not a claim that the revised candidate equals the old pre-revision tree.
- Integrate the exact pushed lower revision additively in the filename-owning worktree, preserving stack117 and both histories.
- Verify only the four filename paths differ from that new lower and that the original filename guard is unchanged.
- Run this candidate's 171 repository cases plus all 13 existing controls, analyzer, and README lint; all pass.
- Record the revised exact-head native CI and full review outcome, keeping draft and auto-merge off.
Named-input revision candidate (superseded by the path-input refresh below): 711d9fbbb5ae8782c931788b62ad8f3b6cb453df, complete tree d42c55a3e1ba1d903bdbcc57e8edc91f9cbc7091. Its four-file diff against the updated lower is 235 insertions and 5 deletions. The 19 filename cases include the original migration scenarios adapted to named inputs, explicit inherit behavior, and explicit empty text overrides. No other lower file differs. This remains an unpublished dependent draft; no readiness or publication gate is removed.
Settings-path prerequisite revision
The accepted public-input rename belongs to Task111/PR109, source 2fc7c584b9bf2bb87e9a79d6516770660b68c99b, tree 97c775596e9b7f80ca6ed29cc2dab695347ab859. That lower source exposes SettingsFilePath and its matching environment forwarding, without a ConfigurationFile metadata/runtime alias, and deliberately retains the old conventional filename. This filename layer inherits the input rename; it does not implement a competing public API change.
- Merge the exact pushed lower revision additively and preserve native stack117 and both histories.
- Adapt only coupled filename guard/test/doc references, including the inherited default-file expectations, while preserving all other lower files exactly.
- Run this candidate's 175 repository cases plus all 13 unchanged controls, analyzer, and README lint; all pass.
- Record the new exact-head native CI and full review outcome, retaining draft/no-auto-merge and existing prerequisite gates.
The initial path-input revision candidate (superseded by the hosted-coverage inheritance below) is adc8ae4acea7776c4bef9c9acc665e83a4f5d4f9, tree 635db082396ce31a70be4e455e9cc487be00d842. It still differs from its immediate lower in only action.yml, src/main.ps1, tests/Release-GHRepository.Tests.ps1, and README.md: 235 insertions and 5 deletions. In action metadata the only upper delta is the conventional default path; the input name and forwarding come from PR109. The guard keeps its predicates/path behavior with the inherited input/variable names. Historical exact-tree and prior-candidate evidence remain separate from this current source.
Final hosted-coverage inheritance
PR109's ordinary workflow-only child d190349c145f4eb99748e39eaf8f2e1104230a11 (tree be3b9d7ba05f4f07bf7ae030696beb2fa55eab85) adds an ephemeral runner.temp settings fixture and always-run cleanup to its existing read-only caller validation. The public input rename still belongs to PR109's 2fc7c5; no runtime/API/default/source-test/README blob changed in this follow-up.
The filename layer inherits that exact child through ordinary merge 13e16a44b810a279387a96c6f203e60e99b710ab, tree 0eba52e96e2e283600e9fd151c34c778a8c49fa0. Its four filename blobs and exact +235/-5 scoped patch are unchanged from the prior path-input candidate. All other lower files are identical; no new API feature or workflow customization is implemented in this upper delta.
- Inherit the final exact lower workflow-only revision additively and verify the unchanged four-path filename patch.
- Rerun this final tree's 175 repository cases plus 13 unchanged controls, analyzer, and README lint; all pass.
- Verify actual hosted loading of the generated file, contrasting named-over-file values, independent file-only policy, and successful preparation/caller/cleanup steps.
- Record the final source head's own native checks and clean review, retaining draft/no-auto-merge and existing prerequisite gates.
The actual caller job reads release-caller.settings.yml under runner.temp. Direct inputs produce minor/ActionInput, cleanup false, both text values empty, and WhatIf true; the file-only CreateMajorTag: false remains effective without an input override, independently proving loading. All three fixture preparation, caller, and cleanup steps succeed. This supersedes the earlier missing-custom-file forwarding-only control without changing runtime behavior or publishing authority.
File-backed standard-values revision
The user superseded the earlier explicit inherit contract: inheritance must be normal omission behavior, and standard release values must come from a settings file rather than action.yml. This resolver change remains owned by Task111/PR109. Its selected design is action-owned src\release.settings.yml, loaded relative to the action script, then optional selected repository policy, then nonempty named inputs. No public magic value, clear flags, mapping input, or second input vocabulary is added. Explicit false remains supported; blank inputs cannot distinguish omission from clearing, so empty text belongs in settings files. Invalid nonempty inputs and invalid file values still fail normally.
The currently pushed source pair remains lower d190349c145f4eb99748e39eaf8f2e1104230a11 and upper 13e16a44b810a279387a96c6f203e60e99b710ab; it is historical evidence for the prior contract, not proof that this new request is implemented.
- Route the exact user correction to the existing resolver owner without changing filename or module interface ownership.
- Define the two filename-specific blank-input controls first; both fail against the old marker/empty-clear contract. Test-only commit
edacaf3d8b05c931b4d723387eff6841cf95bc17remains local and unpushed. - Inherit the actual committed/pushed resolver revision additively and verify the four-path filename boundary.
- Run this candidate's own relevant tests/analyzers and exact-head native checks/review; refresh current adoption records while retaining draft/no-auto-merge and real prerequisites.
Interim file-backed candidate (superseded by the helper-policy deduplication below):cade27b9371995d8926513ec4ca738ab2810e1f5, treec8eb1f610afe272d3a8316b834f801205c541ddf, immediate lower9e1c37073186bb33a1e1a979f97b4af0da0271cb, tree38d198d94b7852d1147fb94a25cabd39624fe84c. The eleven standard values and their parsed types are unchanged, now declared only in the bundled file; no release-setting metadata defaults or inline mapping remain. The bundled resource, resolver, and caller workflow are inherited without an upper change.
This owning candidate passes 195 repository cases plus 13 unchanged controls (208 total), analyzer on four PowerShell files, and pinned README lint. The filename guard remains unchanged and only the four filename paths differ from the new lower (+235/-5). Two prior-contract controls fail before the lower revision and pass after it: blank inputs preserve repository policy and nonempty file text. Exact-head native checks/review and current adoption-record refresh remain in progress.
Final single-source helper policy
The lower owner removed two remaining implicit patch convenience defaults from pure converter/decision helpers in ordinary child a28d7a64685956ec78c766850197fa6420dfc054, tree 74fe0e01f63edd8d37492804fde68e0667710978. Helpers require the validated effective bump; the Action already passes the real resolved file value. The Action's DefaultBump input remains optional. Metadata, bundled standards, controller, caller workflow and README are unchanged from the file-backed revision.
This final lower is inherited additively in 4ab2274462aedfa8161c498caf5859514a32307b, tree 2229aba72dfcfacb1d05f11e69ef31d8481de969. Only inherited helper/helper-test files changed from the interim upper; all four filename blobs, guard behavior, and scoped patch 637fe42c29129b415c8b291cd918957010ae4062619be982e99eb6b3fcd3e120 are unchanged. The four-path filename delta is still +235/-5, with every other lower file preserved exactly.
The final tree passes 197 repository cases plus 13 unchanged controls (210 total), PSScriptAnalyzer on four files, and pinned README lint. Earlier candidate counts and approvals are not reused for this final source. Exact-head upper native execution (197 cases), nine real policy observations, approved review 5910884239 and the final adoption record are verified. Lower final review 5910904940 is COMMENTED with no open issues and requires human validation; it is not approval. A lower pinned-module restoration attempt reported HTTP502 before discovery and executed no tests. The unchanged-source failed-job retry at attempt 2 is now verified: 178 passed, zero failed/skipped/not-run and Executed=True, without a source, dependency or gate change.
Discoverable defaults without bundling
The latest user direction supersedes the bundled-file rename/design. No asset was renamed to default.settings.yml. The user selected blank runtime inputs with documented defaults per input, after verification that native default: injection removes the supplied-versus-omitted distinction. With a native patch default, omission and explicit patch reach the action identically; the runner's userInputs list is private and is not passed to the composite handler. Equality-to-default is therefore not valid override detection.
The supported target remains owned by Task111/PR109: no bundled settings file; one standard-value declaration in action.yml; values displayed in each input description; omitted/blank release-setting inputs keep repository policy; nonempty supplied inputs, including values equal to the standard, override it. No marker, extra flags, mapping input, workflow parsing or prose parser is introduced. Path/runtime defaults remain separate, and the consumer path still resolves from WorkingDirectory (normally github.workspace).
- Verify official metadata documentation and immutable runner8cfa1049f86781d141056082d73802d56cd2b433 input merge/context behavior.
- Capture the user's supported-contract choice and route it to the existing resolver owner.
- Inherit the actual committed/pushed no-bundle revision additively, preserving only the filename delta.
- Verify omitted inputs versus explicit standard-valued inputs, own local/native candidate checks/review, current adoption records and unchanged real gates.
The currently pushed a28d7a6/4ab2274 pair remains valid historical evidence for the preceding bundled design, not proof that this replacement is implemented. No consumer-file path or filename ownership change is requested by this revision.
Current discoverable-metadata candidate: 83d36196d5615596344a761ecad4a179d7927455, tree 95d699c4169725ed52c69313a48fb46d3df86f14, immediate lower 714b801478b5c60565fcfb99ac66b440872f5250, tree b516309bd1041aff174b1ef94b7cd4c46827690d. Both bundled-file names are absent; all11 unchanged typed standards are declared once in private action metadata and displayed in the input descriptions. Native release-setting defaults remain absent intentionally, not replaced by a heuristic or token.
This owning candidate passes 198 repository cases plus 13 unchanged controls (211 total), PSScriptAnalyzer on four files, and pinned README lint. The explicit-standard-value filename regression proves patch input overrides file major before an owned minor label; the omission counterpart retains file policy. The guard is unchanged and only the four filename paths differ (+235/-5), with all other lower files identical. Source-bound native checks and the actual paired invocations are verified. Final upper review 5911365421 is APPROVED/no active issues; lower review 5911340680 is COMMENTED/Needs a closer look/no open issues, not approval. Current adoption records and all genuine draft/prerequisite limits are verified.
Activity
MariusStorhaug commentedon Nov 13, 2026
Implementation is available in draft #116, targeting the real resolver branch rather than main. Owning branch
release-settings-filename, head905ced93d13306c18ddf239d8bc2a02b4b48533a, immediate base3e1b28ee377528c54b0e0ced25df67876144af84.The single ordinary additive commit changes only the four authorized paths (191 insertions, 5 deletions). All four blobs match preserved source
03e20b8293dd8dfb41bead3255930a5edbb2e9bb; the complete cumulative tree is exactlyb2eb47c43236917ba6bc489a9fea391a66f79709. The full-index binary patch equals the acceptedb8767c4to03e20b8filename slice, with every other lower file unchanged.Own-worktree evidence: the lower-reader red control has 16 failures/151 passes; the extracted candidate has 167/167 repository cases and 13/13 existing bootstrap/authentication controls passing, with no skipped cases. PSScriptAnalyzer 1.25.0 reports zero diagnostics on all four source/test files. The existing pinned markdownlint-cli2 0.24.0 README check reports zero issues. The old-reader fixture blobs were checked against actual published v2.0.3 source before execution. GitHub/CLI writes are denied by mocks; the authentication control's real Git command only expands an anonymous URL locally.
Current-head native CI and the explicitly requested native Copilot review are still being inspected. This progress does not claim production publication, compatible template delivery, current human approval, or readiness. Draft and no-auto-merge remain; the native 115 -> 111 -> 112 dependency chain is unchanged. No release label, version tag, release, publisher, rule, permission, or automation setting was changed.
MariusStorhaug commentedon Nov 13, 2026
Bounded filename extraction verification is complete at
905ced93d13306c18ddf239d8bc2a02b4b48533a; the focused draft PR contains the full adoption and source-preservation record.The native current-head result is six successful check runs plus 13 successful lint status contexts. Hosted Pester confirms 167 passed, zero failed/skipped. The default WhatIf caller, repository linter, actions analysis, CodeQL, and native review also pass. The complete native review submitted
APPROVEDon this exact head at2026-11-13T19:22:17Z, with no active issues and no inline comments. This is automated review, not human sign-off or permission to publish. Own-worktree 167 repository cases, 13 existing controls, analyzer, and pinned README check also pass; no inherited old-head result substitutes for those runs.Final local and GitHub readback verifies one ordinary commit, exact parent
3e1b28ee377528c54b0e0ced25df67876144af84, complete treeb2eb47c43236917ba6bc489a9fea391a66f79709, exactly the four prescribed original blobs, exact accepted filename-patch equality, and a clean worktree. No other lower file differs. The lower owner registered native stack117, ordered #109 -> #116, with ultimate basemain; the focused PR still targets the immediate resolver branch. Both PRs remain draft with auto-merge off and unchanged heads.Task 115 remains open and natively blocked by Task 111, which remains blocked by Task 112. Human review, prerequisite delivery/enforcement, authorized engine publication, and verified compatible template/consumer adoption remain distinct gates. No compatible updated template is claimed. No live publication, release label, tag/release mutation, merge, or rules/permissions/automation change was performed. Lower 109/111 records remain with their separate owner.
MariusStorhaug commentedon Nov 15, 2026
The requested PR109 interface revision is in progress: individually named action inputs replace the structured
CallerOverridesinput, withinheritdefaults to preserve omitted repository inheritance and explicit false/empty values. The lower owner retains that resolver work in Task111/PR109; this Task retains only its dependent filename integration.The original exact four-blob/full-tree extraction proof remains historical evidence for
905ced93d13306c18ddf239d8bc2a02b4b48533a, not validation of the next revised candidate. In this owning worktree, the filename-specific tests now exercise named minor/false overrides, custom-path WhatIf override, and explicit empty text overriding the conventional file. The old controller reproduces three expected failures; six invalid-file controls still pass. These test-first commits remain local and unpushed until the actual lower implementation passes them.After the lower revision is committed and pushed, the filename layer will be synchronized additively, its exact four-path scope checked, and its own relevant validation and source/evidence record refreshed. Both PRs remain draft; stack117, the new-only major decision, no-auto-merge, and the 115 -> 111 -> 112 gates are not changed by this progress update.
MariusStorhaug commentedon Nov 15, 2026
The named-input prerequisite refresh is verified and pushed in PR116: head
711d9fbbb5ae8782c931788b62ad8f3b6cb453df, treed42c55a3e1ba1d903bdbcc57e8edc91f9cbc7091, immediate lower47202d7c2f350ae67fda2d5d9e328be3b0d3d492. The upper diff remains exactly the four filename paths (+235/-5); all other lower files are identical and the original filename guard is unchanged. The former exact-original-tree proof is retained as historical extraction evidence, not reused for this revised source.This owning candidate passes all 171 repository cases plus 13 existing controls, analyzer, and README lint. Hosted Pester also confirms 171 passed with zero failed/skipped. All six current-head check runs and 13 lint contexts succeed. The real runner caller job verifies default omission and the six named-input results, including false and both empty strings. The complete revised-head review is APPROVED with no active issues or inline comments; this is automated review, not human sign-off or publication authority.
The full PR record now describes the direct named-input adoption, inheritance/explicit-empty semantics, current base/head/tree/blobs, historical/current proof boundary, actual checks, and retained publication/template limits. Both PRs remain draft with auto-merge off; the native 115 -> 111 -> 112 chain and stack117 order remain intact. No publisher, tag/release, template, rule, permission, or automation change was made.
MariusStorhaug commentedon Nov 15, 2026
The current source is verified at
adc8ae4acea7776c4bef9c9acc665e83a4f5d4f9above the PR109-owned input rename2fc7c584b9bf2bb87e9a79d6516770660b68c99b. Own 175 repository cases plus 13 unchanged controls pass; analyzer/README and all current source CI checks pass.The first current-head review found stale migration wording in the PR body, not a source defect. The body now requires
ConfigurationFile->SettingsFilePathwith the compatible reader, preserves intentional custom-path values, and uses the new input in all post-upgrade examples. The inline thread was replied to and resolved after readback. A fresh review round is requested; no clean new-round outcome is claimed yet.The actual caller job selects the new
SettingsFilePathand correctly reports the intentional custom file as absent, then applies explicit named values with WhatIf true. This proves selected-path forwarding, not loading an existing file in that job. Real file loading, literal paths, and invalid settings are covered by the repository suite. The filename/API topic boundary and all draft/no-auto-merge/prerequisite limits remain unchanged.MariusStorhaug commentedon Nov 15, 2026
The
SettingsFilePathrename remains owned by PR109/Task111 at2fc7c584b9bf2bb87e9a79d6516770660b68c99b(tree97c775596e9b7f80ca6ed29cc2dab695347ab859). This filename layer only inherits it: current upperadc8ae4acea7776c4bef9c9acc665e83a4f5d4f9, tree635db082396ce31a70be4e455e9cc487be00d842. The action metadata delta against the lower is exactly one default-path replacement. Only the four filename paths differ (+235/-5); all other lower files are identical, and the guard predicates/path behavior are preserved with the inherited input references.Own validation passes 175 repository cases plus 13 unchanged controls (188 total), analyzer and README lint. Hosted Pester also confirms 175/0failed/0skipped; every current native check and all 13 lint contexts succeed. The real runner proves the new input selects the intentional absent custom path and preserves named values; existing-file loading is covered by controlled repository tests rather than falsely attributed to that caller step.
The stale migration-note finding was fixed in the PR body, replied to and resolved. The complete clean current-head review is APPROVED, reports no active issues, and confirms the earlier issue resolved. All post-upgrade examples use
SettingsFilePath, and custom path values are explicitly preserved. No source change was needed for that documentation finding.Both PRs remain draft with auto-merge off and only release:major. Native stack117 and the 115 -> 111 -> 112 chain remain. Human review, enforcement, authorized publication, and compatible template/consumer adoption are not inferred from these checks. No version/tag/release, publisher, rule, permission, automation, unrelated source, or PR merge change was made.
MariusStorhaug commentedon Nov 15, 2026
Final path-input adoption and inherited coverage are verified at upper
13e16a44b810a279387a96c6f203e60e99b710ab/ tree0eba52e96e2e283600e9fd151c34c778a8c49fa0, immediate lowerd190349c145f4eb99748e39eaf8f2e1104230a11/ treebe3b9d7ba05f4f07bf7ae030696beb2fa55eab85. The public input rename remains PR109-owned at2fc7c5; PR116 only changes the conventional filename and coupled guard/tests/docs. Its four filename blobs and exact +235/-5 patch remain unchanged after the workflow-only inheritance; all other lower files are identical.This final tree passes 175 repository cases plus 13 unchanged controls, analyzer, and README lint. Six exact-head native check runs and all 13 lint contexts succeed. The real caller reads an ephemeral settings file, demonstrates contrasting named-over-file values and independent file-only
CreateMajorTag: false, and successfully prepares, runs, and removes that file. Caller evidence.The complete final upper review is APPROVED with no active issues. The earlier stale adoption-record finding remains resolved; new-name examples and preserved custom paths are verified in the final PR body. The complete final lower review is COMMENTED/Needs a closer look, not approval: no open issues, but human validation of privileged publishing, live permission safety, release behavior, and immutable adoption is still required. Lower review threads are resolved.
The full PR record now carries the final source/coverage/review evidence without reusing predecessor approval. Both drafts, only release:major, no-auto-merge, stack117 order, and 115 -> 111 -> 112 prerequisites remain. Task115 stays open for its dependent reviewed delivery; no publication, merge, version/tag/release, permission, ruleset, or automation change was performed.
MariusStorhaug commentedon Nov 15, 2026
The requested no-marker/file-authoritative contract is complete in the inherited resolver. Final lower:
a28d7a64685956ec78c766850197fa6420dfc054, tree74fe0e01f63edd8d37492804fde68e0667710978. Final filename candidate:4ab2274462aedfa8161c498caf5859514a32307b, tree2229aba72dfcfacb1d05f11e69ef31d8481de969. Standards come only from the action-ownedsrc\release.settings.yml, then optional repository policy, then known nonempty named inputs. No omission marker or inline standards mapping remains; omitted/blank inputs keep file policy, explicit false still overrides, and empty text is configured in a settings file. Pure helpers no longer choose an implicit patch; the Action still has an optional DefaultBump input and passes its resolved file value.This owning final tree passes 197 repository cases plus 13 unchanged controls (210 total), PSScriptAnalyzer and pinned README lint. Six exact-head native checks and all 13 lint contexts succeed. Hosted Pester actually runs 197/0failed/0skipped. Real caller evidence proves bundled and repository files are read, nonempty minor/false/WhatIftrue overrides apply, blank text inputs retain yyyyMMdd/v, a file-only false setting survives, and preparation/cleanup succeed. The complete current-head review is APPROVED with no active issues; no upper threads remain unresolved.
The lower's first pinned-module restore returned HTTP502 before discovery and executed no tests. Its unchanged-source failed-job retry genuinely executes 178/0failed/0skipped/0notrun with Executed=True, independently verified using explicit attempt2 logs; no dependency or gate was changed. That result is separate from all predecessor counts and approvals.
The upper remains exactly the same four filename paths (+235/-5), with the original guard unchanged and bundled data/resolver/helpers/workflow inherited intact. Parsed standard values/types are preserved for all11 keys. The final PR body now gives the corrected file-first precedence and blank-input/empty-file-value migration without recommending a magic value. Earlier marker-based snapshots remain historical evidence only.
Both PRs stay draft with only release:major and auto-merge off. Stack117 and 115 -> 111 -> 112 remain; no live publication, human approval, compatible template or required enforcement is inferred. No PR merge, version/tag/release, permission, ruleset or automation-setting change was performed. Lower109/111 review records remain with their owner.
MariusStorhaug commentedon Nov 15, 2026
The user-selected supported contract is complete in PR109 and inherited here. There is no bundled defaults file or renamed default.settings.yml asset. Effective standard defaults are displayed in all11 release-input descriptions, declared once in private action metadata, and never injected as native runtime policy defaults. Omitted/null/blank values keep repository policy; nonempty supplied values override it, even when equal to the advertised standard. False stays explicit; whitespace/invalid layers validate normally. No presence flag, equality heuristic, workflow parser, prose parser, marker, clear flag or public mapping input was added.
Final lower:
714b801478b5c60565fcfb99ac66b440872f5250/ treeb516309bd1041aff174b1ef94b7cd4c46827690d. Final upper:83d36196d5615596344a761ecad4a179d7927455/ tree95d699c4169725ed52c69313a48fb46d3df86f14. The upper remains exactly four filename paths (+235/-5), guard unchanged, all other lower files identical. Standard values and parsed types are preserved for all11 keys. Consumer SettingsFilePath still resolves from WorkingDirectory, normally github.workspace; its final default remains .github\release.settings.yml.Own211cases (198repository+13unchangedcontrols), PSScriptAnalyzer and pinned README lint pass. Six exact-head native checks and13lintcontexts succeed; hosted Pester actually executes198/0failed/0skipped. Actual paired caller evidence proves existing-file major with omitted bump remains major/RepositorySetting, while explicitpatch equal to the standard becomes patch/ActionInput. Each invocation has nine anchored observations including standards/file reading, false override, file-only policy, blank-text retention and WhatIftrue. Fixture preparation, both invocations and cleanup succeed.
The complete final upper review is APPROVED/no active issues. The complete lower review is COMMENTED/Needs a closer look/no open issues, not approval; authorized human validation of privileged release behavior remains. All existing threads are resolved. The final PR116 adoption record now describes the actual no-bundle/description-default/native-blank tradeoff, new-name migration, exact current source/evidence and unchanged real limits. Earlier bundle/marker designs remain historical, not current validation.
Both PRs remain draft with only release:major, auto-merge off, native117 order and115 ->111 ->112 intact. No live publication, human approval, compatible template or required enforcement is inferred; no PR merge, version/tag/release or repository rule/permission/automation setting changed. Lower109/111 records remain with their owner.