LIST FOLDERS, constant credentials for $metadata, and dark-mode filter popovers

[ako]

Three fixes from the mxcli-formula1 findings, plus the symptom rows for them.

LIST FOLDERS — read a module's layout back (open issue #2)

MOVE could place a document in a folder, but nothing could read the placement back: SHOW STRUCTURE groups by document type at every depth and never names a folder, DESCRIBE answers for one document at a time. So a move could not be confirmed, and an intended layout could not be diffed against the real one, without opening the .mpr as SQLite.

Administration
  System Administration  [3]
    Page ActiveSessions
    ...
  User Management  [0]
  User Management/Admin  [9]
    Microflow ChangePassword
    ...
  _Docs/v4.3.2  [0]

(6 folder(s), 18 document(s))

Three properties are load-bearing for the diff use case, not cosmetic:

• empty folders are listed ([0]) — a listing that hid them could not round-trip against an intended layout;
• documents still at the module root appear under (module root) — what is not filed yet is the thing you most want to notice;
• ordering is stable, so a diff between two runs shows only real movement.

Documents are indexed by ContainerID across every list call the backend offers, each best-effort: a backend that cannot answer one kind yields a listing missing that kind rather than no listing. --json gives one row per document (Module, Folder, Kind, Document).

Chosen as a new command over restructuring SHOW STRUCTURE, whose three depth levels are rendered by a dozen separate loops that agents already depend on. list is the verb per design-mdl-syntax.md; show folders is accepted as the legacy spelling.

OData: resolve constant credentials for the $metadata fetch

Follow-up to the earlier fix that made literal credentials work. HttpUsername: '@Module.ApiUser' still returned 401 and an empty client, because '@Module.ApiUser' is a STRING_LITERAL — the visitor's isLiteral flag said "literal" and the fifteen characters @Module.ApiUser went out as the username. The unresolved-credential note did not fire either, since as far as the code knew nothing was unresolved.

The fix resolves the constant's design-time default, which is exactly what Studio Pro sends on the same fetch. Three spellings now work ('v', @M.C, '@M.C'), and a dotted literal such as a password containing a dot is not mistaken for a reference.

Theme: dark-mode filter-operator popovers

An app themed dark still showed light-mode drop shadows under the datagrid's filter-operator popover and dropdown lists. The generated widget layer re-pointed .column-selectors but not the four rules in _datagrid-filters.scss that bake the same two-layer shadow — each already takes its background from --bg-color-secondary, which is why it read as a partial fix rather than an untouched widget. Verified in the compiled CSS by line number (30794 vs 27765), not in the source.

Verification

Tier	Result
Unit tests	pass; the LIST FOLDERS control run (stub out empty folders + the root bucket) confirms the assertions detect the defect
mxcli check on the doctype script	clean, 21 statements
Full doctype integration gate (real mxbuild)	ok … 609.122s, exit 0
18-folder-examples on modelsdk and legacy	PASS
Live against a real project	both verbs, with/without IN, --json
Theme	applied to a real project, rebuilt, grepped theme.compiled.css

Docs: syntax topic folders (+ SeeAlso from move), quick-reference rows, a "Reading the Layout Back" section in organize-project.md, a doctype example, and three symptom rows in fix-issue.md.

Known inconsistency, not addressed here

show structure in Administration prints nothing for a system module without all, while list folders in Administration lists it. That divergence predates this change and is worth its own decision rather than a silent alignment.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JXnEgoc2NQP1Y2TWMCMXC4

---

Generated by Claude Code