Nested <use-package> inside a user package no longer cascades (regression between LiiiSTEM 2026_2.6 and 2026_3.2)

[Matthias-A-Steiner]

Nested <use-package> inside a user package no longer cascades (regression between LiiiSTEM 2026_2.6 and 2026_3.2)

Summary

A user package (unicode-core.ts) that itself calls <use-package|...> to pull in two further sub-packages (unicode-figures.ts, unicode-environments.ts) loads correctly in GNU TeXmacs 2.1.5 and in LiiiSTEM 2026_2.6, but fails to cascade-load its dependencies in LiiiSTEM 2026_3.2. Manually adding all three packages to the document's own style/package list works fine in both versions — only the nested use-package call (a package loading further packages on its own) is affected.

Environment

• App: LiiiSTEM (Mogan/MoganLab build)
• Working version: 2026_2.6 (clean install, works as expected)
• Broken version: 2026_3.2 (same document, same packages, fails)
• OS: macOS 14.8.9 (Apple Silicon, M3)
• TEXMACS_HOME_PATH equivalent: ~/Library/Application Support/liiilabs/
• Reference (unaffected): GNU TeXmacs 2.1.5, works correctly

Package layout

~/Library/Application Support/liiilabs/packages/
└── TST-core/
    └── unicode/
        ├── unicode-figures.ts
        └── unicode-environments.ts
    └── unicode-core.ts

unicode-core.ts contains:

<use-package|TST-core/unicode/unicode-figures>
<use-package|TST-core/unicode/unicode-environments>

Steps to reproduce

1. Install the three attached style/package files into the layout shown above (adjust the path if TEXMACS_HOME_PATH differs on your system).
2. Create a new document.
3. Add only unicode-core to the document's package list (via Focus toolbar or document preamble) — do not add unicode-figures or unicode-environments directly.
4. Insert the macro <unicode-core-marker> (or any macro defined in unicode-figures.ts / unicode-environments.ts, e.g. <big-unicode-table|...>, <unicode-example|...>).

Expected behavior

unicode-core.ts's own <use-package> calls should transitively load unicode-figures.ts and unicode-environments.ts, so macros defined in either sub-package render normally — as they do in GNU TeXmacs 2.1.5 and in LiiiSTEM 2026_2.6.

Actual behavior (2026_3.2 only)

Macros from the two sub-packages are treated as undefined and render as raw unexpanded markup (e.g. ⟨big-unicode-table|...⟩, ⟨unicode-example|...⟩) instead of the intended typeset output. The problem disappears the moment unicode-figures and unicode-environments are added directly to the document's package list alongside unicode-core — so the packages themselves are found and load correctly; only the automatic cascade triggered from inside another package's body fails.

What we've ruled out

• Missing .ts extension in use-package: not the cause — use-package resolves the extension automatically in both editors, same as in stock TeXmacs.
• Wrong directory / nesting: not the cause — the TST-core/unicode/... path referenced by use-package matches the actual on-disk layout exactly.
• File permissions: one file briefly had 600 instead of 644 permissions during debugging; this was corrected and made no difference. Both sub-packages fail to auto-load together, and both load fine manually, which is inconsistent with a permissions-only explanation.

Suspected cause

LiiiSTEM/Mogan bumped its underlying Goldfish Scheme engine one or more times between the 2026_2.6 and 2026_3.2 builds (e.g. the v17.11.21 → v17.11.32 upgrades visible in the MoganLab/mogan commit history). Engine bumps in this range have already been shown to cause regressions in previously-working features (e.g. the gnuplot fix that immediately followed the v17.11.32 bump), so a change in how nested/recursive use-package resolution is handled by the new engine seems like a plausible cause, though this is not confirmed.

Attachments

• unicode-core.ts
• unicode-figures.ts
• unicode-environments.ts

(minimal reproduction — please let us know if a smaller repro would help)

unicode-core.ts

unicode-figures.ts

unicode-environments.ts

[priyanshusky0]

Hi @Matthias-A-Steiner ,
I came across this issue and would be interested in investigating and fixing the regression in nested use-package resolution between LiiSTEM 2026_2.6 and 2026_3.2. I can start by reproducing the issue, narrowing down the Goldfish Scheme/Mogan regression, and preparing a fix with a regression test.
If you’re not already working on this, would you be able to assign the issue to me? I’d be happy to take it up.

[Matthias-A-Steiner]

Hi, @priyanshusky0,

by all means, please do go ahead, as I'm not a Scheme programmer. Thanks for taking care of the issue.

Cheers, Tilda

[priyanshusky0]

Hi @Matthias-A-Steiner , thanks again for letting me take this up. I’ve opened the PR above with the fix and a regression test.
I reproduced the issue using the same package structure from #4453, where unicode-core.ts loads unicode-figures.ts and unicode-environments.ts through path-qualified use-package calls under $TEXMACS_HOME_PATH/packages/.
On main, the nested packages fail to resolve. With the patch, they are correctly found and loaded, and their macros are available in the environment.
I also added regression coverage for nested user packages, document-relative packages, home plugin packages, style-root resolution, package-root precedence, bare package names, and missing packages. The test goes from 4 passed / 5 failed on main to 9 passed / 0 failed with the patch.
I additionally tested the original three .ts files attached to the issue end-to-end. Loading only unicode-core now correctly resolves all of its sub-packages, so the reported issue is fixed.
Thanks again for pointing me to the issue. I’d appreciate your feedback on the approach.

[Matthias-A-Steiner]

Hi @priyanshusky0 thanks for fixing this so thoroughly. I've read your PR which I consider quite impressive work. Let's hope the request will be accepted and implemented pretty soon.

Cheers, Tilda