`./assets` in the `exclude` field of `typst.toml` actually matches `**/assets`

Description

https://github.com/typst/packages/blob/8785ec6f6da2e7896db08857d38d6ed4cddebce8/docs/manifest.md?plain=1#L68

It looks like an array of globs is the only description for the format of the exclude field in typst.toml.
This ambiguity cause problems.

https://github.com/QuadnucYard/ourchat-typ/issues/3 is an example.
This package has the following file structure.

• /typst.toml
• /assets/ (to be excluded)
• /src/
  • /src/assets/ (to be included)

The package specifies ./assets, but surprisingly, it matches both /assets/ and /src/assets/.

exclude = ["./assets"]

Analysis

The bundler trims the ./ prefix, and uses a library for .gitignore to parse the glob.
As a result, ./assets becomes assets, and matches recursively.
https://github.com/typst/packages/blob/8785ec6f6da2e7896db08857d38d6ed4cddebce8/bundler/src/main.rs#L336
(introduced in https://github.com/typst/packages/commit/b41d4831f9e4f54a71c25336b658021a6824fc7a)

Workaround

Use /assets.
(not confirmed yet)

Confirmed with https://github.com/typst-community/dev-builds/releases/tag/packages-bundler-main.2025-12-10.8c2f3eb.

Links

Discord

Start with bundler/src/main.rs around line 336 and compare its exclude handling with the format described at docs/manifest.md line 68. Reproduce the behavior using the package layout in the report, including /assets and /src/assets. Done means the intended path-matching behavior is implemented and the exclude-field documentation is no longer ambiguous.