fix: preserve original app name as manifest display name

[srtaalej]

Summary

• Separates the directory name (kebab-case) from the manifest display name (original user input) during app creation
• Manifest display names (display_information.name, bot_user.display_name, and Deno SDK Manifest({ name })) now preserve the user's original input instead of using the kebab-case directory name
• package.json and pyproject.toml names remain kebab-case per npm/Python conventions

Behavior

$ slack create              # random name → path "vibrant-panther-540/", manifest "vibrant-panther-540"
$ slack create my-app       # path "my-app/", manifest "my-app"
$ slack create "My App"     # path "my-app/", manifest "My App"

Test plan

• Test_App_UpdateDefaultProjectFiles validates manifest files get the display name while package.json/pyproject.toml keep kebab-case
• Test_RegexReplaceAppNameInManifest updated to reflect display name input
• Manual: slack create "My App" → verify manifest display name is "My App", directory is my-app/, and package.json stays my-app

[codecov]

Codecov Report

❌ Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 71.27%. Comparing base (7c7394c) to head (39cdaad).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/pkg/create/create.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #521   +/-   ##
=======================================
  Coverage   71.26%   71.27%           
=======================================
  Files         222      222           
  Lines       18682    18683    +1     
=======================================
+ Hits        13314    13316    +2     
- Misses       4188     4189    +1     
+ Partials     1180     1178    -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[zimeg]

@srtaalej Thanks for getting this started 👾 ✨

I'm hesitant on this approach and am wondering if we instead separate how arguments and flags are parsed at this point?

Some issues I ran into are in comments but I'd like to share how I think about the "create" command:

$ slack create           # Generates a random app name as current
$ slack create my-app    # Keeps path "my-app" and manifest "my-app"
$ slack create "my App"  # Uses path "my-app" and manifest "my App"

🧰 Additional cases might complicate this but it's a good time to untangle this perhaps? I'm curious also if adding the --outdir flag makes parts of this more clear, while still supporting the happiest path simple cases?

[zimeg]

🔍 issue: We might want to avoid changing the app name format altogether if this is provided in flags? Forgive me if I'm not understanding requirements right, but this app manifest for example might break with replacements:

Translator - Translate Languages

🔗 https://slack.com/marketplace/A8KHN4EDV-translator-translate-languages

[zimeg]

🐍 ramble: Apps I keep might not fare well for additional example: "TIM", "TOM", or "snaek" have strange cases.

[zimeg]

@srtaalej This is running alright but I'm not certain the expected behavior matches the PR description and title since IIRC we're now avoiding title case defaults?

Leaving a few thoughts before approving and I also think a changelog toward this is best? Perhaps a standalone "bug" label too unless new featuresets are included too?

[zimeg]

🌟 praise: Nice! Keeping these separate makes it much easier to think about for me!

[zimeg]

🧠 praise: Nice separation for project titles!

[srtaalej]

@zimeg updated the pr description and tests!