[Solution] FancyNames option is dead code

[ChrisonSimtian]

Problem

The FancyNames option for the [Solution] strongly-typed accessor does nothing, two ways: SolutionAttribute exposes no FancyNames property (only List/GenerateProjects), so [Solution(FancyNames = true)] won't compile; and even when forced on, the emitter strips the fancy ٠ separator so output is identical to the default. Surfaced in #442.

Outcome

FancyNames is either a working, settable option or removed entirely — no dangling reads left in the emitter, generator, or console.

Acceptance criteria

• [Solution(FancyNames = true)] compiles and changes accessor names (Foo.Bar → Foo٠Bar), or the concept is removed across SolutionEmitter, StronglyTypedSolutionGenerator, and Fallout.Solution.Codegen.
• A spec in Fallout.Solution.Codegen.Specs pins the chosen behaviour.

Notes

• No-op root cause: GetEscapedName does .Replace(".", "٠") then .ReplaceRegex(@"[^A-Za-z0-9_]", "_") (ASCII-only), which deletes the ٠ — src/Fallout.Solution.Codegen.Emit/SolutionEmitter.cs:91.
• Attribute missing the property: src/Fallout.Common/Attributes/SolutionAttribute.cs. Generator read: src/Fallout.SourceGenerators/StronglyTypedSolutionGenerator.cs:52.
• Non-breaking either way.

[ITaluone]

Why do this "fancy name" even exist? What is the use case?

[ChrisonSimtian]

From what I understand, it prettifies the intellisense sugar in the generated solution class.
Lets say you got a structure like this and want to run stuff in nuke/fallout against this solution:

  MyApp.sln
  ├─ MyCompany.Web.Api      (project)

you can do stuff like

MyCompany_Web_Api.Build();

or with the fancyNames you can add a bit of sugar and make it look like this:

MyCompany٠Web٠Api.Build();

[ITaluone]

Ahh.. This is nice! I vote for keep and actually implement it properly :)

[ChrisonSimtian]

we can definitely look into it, but apparently its not working at the moment (hence why claude flagged it in the first place)
I leave this open as both a bug and enhancement. I'm doing some heavy refactoring in that area at the moment, might just fix it while I'm at it ;-)

The only problem I see with that character at the moment is ... where the heck on my keyboard do I find it?! (And I already got a german, a US AND a Maori keyboard in front of me xD)

[ITaluone]

Yeah.. the only way is to rely on IntelliSense...

I don't any other key, which is on a german/english keyboard and has no meaning to C#...

Edit: the only char I could find was µ and german umlauts.. but this seems really odd...

[ChrisonSimtian]

little side note: this isnt really "fancy names" but more like "replace illegal characters with legal characters" in order to make C# happy.

And another thing is choice of character. Either we pick something thats widely supported but comes with its own problems or something thats not necessarily widely supported but can be used at any position of an identifier.