`kit init` includes hidden files in Kitfile

[amisevsk]

Describe the bug
Running kit init will attempt to place all files in the current directory inside the Kitfile. This includes hidden files, particularly OS-specific files like MacOS's .DS_Store.

In some cases, this can lead to adding an entire opaque code section to the Kitfile solely to hold the hidden files.

Kit should

1. Ignore OS-specific files such as .DS_Store and similar in kit init; i.e. files not added by the user
2. Exclude OS-specific files even when a directory path might include them (e.g. a code layer with path: . that includes non-ignored iles)
3. (Maybe) Ignore packing hidden files by default, to be re-enabled via flag

To Reproduce

1. Run kit init in a directory containing hidden files
2. In all likelihood, notice a 'catch-all code layer (path: .`) that's added to include them, even when not necessary

Version
latest

Additional context
N/A

[Kabirat000]

Hi! I'm interested in taking this on.

From what I understand, the fix would involve:

1. Creating a list of patterns to ignore (OS-specific files)
2. Filtering these out when kit init scans directories
3. Maybe adding a flag to control this behavior

Before I start, a few questions:

• Is this issue still available?
• Should the ignore list be hardcoded or configurable?
• Do you want me to follow the existing .gitignore patterns?

I'll read through the contributing guidelines and get familiar with
the codebase. Looking forward to working on this!

[arnab2001]

@amisevsk still available? I'd like to pick this up. if its unclaimed.

From reading the codebase, the fix is in genDirListingFromPath() in pkg/lib/kitfile/generate/filesystem.go, it currently includes everything that passes IsRegular() with no hidden/OS-file filtering.

My proposed approach:

• Filter at scan time (before file classification), not at pack time
• Hardcode a list of known OS-specific files (.DS_Store, Thumbs.db, desktop.ini, .Spotlight-V100, .Trashes, $RECYCLE.BIN)
• Skip hidden files (dot-prefixed names) by default — this directly addresses point 3 from the issue
• No new flag or config needed unless you'd prefer one; the issue marks it as "maybe"

Does this align with what you had in mind? Happy to start once confirmed.

[rishi-jat]

Hey @amisevsk , please review PR - #1099 Thanks!