Fix duplicate `.well-known` path causing Laika parser errors during site build

[Piyush-t24]

While trying to run the website locally using:

scala-cli build.scala -- serve

I encountered a Laika parsing error caused by duplicate paths under .well-known:

Duplicate path: /.well-known/openpgpkey/policy
Duplicate path: /.well-known/security.txt

After investigating the build configuration, I noticed that the input tree includes:

.addDirectory("src")

and also explicitly adds:

.addDirectory("src/.well-known", Path.Root / ".well-known")

There is a comment in the code stating:

// Laika skips .dotfiles by default

which suggests that .well-known would normally be ignored when scanning src.
However, in my local setup it appears that the .well-known directory is already included through .addDirectory("src"), so adding it again results in duplicate paths during parsing.

When I comment out the following line:

.addDirectory("src/.well-known", Path.Root / ".well-known")

the site builds and runs successfully.

I wanted to ask whether this explicit directory mapping is still required with the current Laika version, or if it may now be redundant.

For reference, I have attached the stack trace produced during the build.

Happy to adjust the fix if there is a preferred approach.

[Piyush-t24]

Hi @armanbilge ,

After further investigation, the issue appears to be caused by platform differences in how hidden files are handled.

Laika’s default hidden filter relies on Files.isHidden. On Linux/macOS, directories starting with . (like .well-known) are treated as hidden and therefore skipped when scanning src.

On Windows, however, Files.isHidden checks the DOS hidden attribute instead of the leading . convention. As a result, .well-known is not considered hidden and gets included when scanning src.

Because the build configuration also explicitly adds:

.addDirectory("src/.well-known", Path.Root / ".well-known")

the directory ends up being included twice on Windows, which causes the duplicate path errors.

A fix has been proposed in PR #614 that excludes .well-known from the main src scan while keeping the explicit mapping so the behavior remains consistent across Windows, Linux, and macOS.