chore(394,395): record promoted potential entries for PR #391 follow-ups#396
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/features/potential/promoted/2026-07-20-utilitiescs-test-cs2002-duplicate-compile-entry.md, the promotion record behind issue Bug: utilitiescs-test-cs2002-duplicate-compile-entry #394 (CS2002 duplicate<Compile>entry inUtilitiesCS.Test.csproj).docs/features/potential/promoted/2026-07-20-system-reactive-7-packages-config-migration.md, the promotion record behind issue Refactor: system-reactive-7-packages-config-migration #395 (System.Reactive 7.0packages.configincompatibility warning).Why
The feature-promotion lifecycle requires each potential entry promoted to a GitHub issue to have its promotion record committed under
docs/features/potential/promoted/. Both entries were promoted via the drm-copilot promotion tooling on 2026-07-20; this PR lands the resulting artifacts so the repository audit trail matches the open issues. Direct pushes tomainare blocked by repository rules, so the artifacts are delivered through this pull request.What Changed
docs/features/potential/promoted/(+105 lines total, no deletions).Architecture / How It Fits Together
Not applicable; no runtime components are affected. The files are inputs to the feature-promotion lifecycle (potential entry → issue → active feature folder) and will be referenced when issues #394 and #395 are picked up.
Verification
origin/main(merge base793508e7); changed-files overview confirms a docs-only diff of the two listed files.Backward Compatibility / Migration Notes
None. Additive documentation only.
Risks and Mitigations
Review Guide
docs/features/potential/promoted/2026-07-20-utilitiescs-test-cs2002-duplicate-compile-entry.md— bug promotion record for issue Bug: utilitiescs-test-cs2002-duplicate-compile-entry #394.docs/features/potential/promoted/2026-07-20-system-reactive-7-packages-config-migration.md— refactor promotion record for issue Refactor: system-reactive-7-packages-config-migration #395.Follow-ups
<Compile>item inUtilitiesCS.Test.csproj.GitHub Auto-close