rebrand skill leaves the developer-cli .DotSettings symlink dangling → Developer CLI lint CI fails

[raix]

Contact Details

No response

Bug description

Problem

developer-cli/DeveloperCli.slnx.DotSettings is a symlink to the application solution's settings so the CLI shares the same inspection config:

developer-cli/DeveloperCli.slnx.DotSettings -> ../application/PlatformPlatform.slnx.DotSettings

The rebrand skill (STEP 5) renames the application solution settings:

git mv application/PlatformPlatform.slnx.DotSettings application/<SolutionName>.slnx.DotSettings

…but never repoints the symlink. After a rebrand the symlink dangles, so JetBrains InspectCode can't load the shared suppressions and falls back to
defaults. The .Global rules that the shared settings demote to HINT (AutoPropertyCanBeMadeGetOnly.Global, ClassNeverInstantiated.Global,
MemberCanBePrivate.Global) revert to note severity, get reported, and the Developer CLI workflow (developer-cli.yml) fails its lint step — with
no code change involved.

Reproduce

1. Run the rebrand skill on a fork.
2. Push; the Developer CLI workflow lint step fails with .Global "never instantiated / can be made private / can be made get-only" notes.
3. ls -la developer-cli/DeveloperCli.slnx.DotSettings shows it pointing at the old PlatformPlatform.slnx.DotSettings name (dangling).

Fix

Repoint the symlink as part of STEP 5, after the git mv:

ln -sf ../application/<SolutionName>.slnx.DotSettings developer-cli/DeveloperCli.slnx.DotSettings

Also add developer-cli/DeveloperCli.slnx.DotSettings to the STEP 12 expected-diff list so the audit catches it.

---

Severity

Low

Is this bug security related?

• This bug is related to security

Code of Conduct

• I agree to follow this project's Code of Conduct

[linear]

PP-1320