Pin latest liter-llm with UAR transport boundary compatibility

.prometheus/decisions.md

@@ -290,3 +290,49 @@ that the `compass` pin must be a tag on a clean commit rather than the dirty sid
 **Decision.** Added `aarch64-pc-windows-msvc` to `dist-workspace.toml` targets with a native `windows-11-arm` runner. Branch `feat/windows-arm64-target`, commit `3a8d182`, unpushed.
 
 **Why.** the-boss ships `electron-builder --win --x64 --arm64`. The target list covered `x86_64-pc-windows-msvc` only, so an arm64 Windows build would have had no artifact to download. The sibling compass fork already builds both Windows arches. No workflow regeneration is needed: `release.yml` builds its matrix at runtime from `dist plan` and carries no config-freshness gate — verified by reading the generated file. `dist` is not installed locally, so CI is what confirms the new job appears.
+
+## 2026-09-30 — The Boss consumes the latest committed liter-llm fork
+
+**Operator instruction:** update liter-llm and prometheus-skills-mini submodule links to
+the latest fork revisions for the next The Boss build. The mini baseline is
+`ac99730e2b7b5cb22079d984abc0fb92fb911aff` from
+`Prometheus-AGS/prometheus-skills-mini/main`; its 100 skills and executable dependencies
+remain intact. The accepted liter-llm source is
+`GQAdonis/liter-llm@12a2fae9675e34b88e9373caa2bca9959f416493`, fetched from the fork's
+`main` on 2026-09-30. This supersedes the `4f25d39f0075656b70bf945880d6033beda6d663`
+gitlink for this explicitly requested release payload.
+
+**Authority remains visible:** `versions.toml` is operator-authored and is not edited
+by this update. Its liter-llm line still records the prior `4f25d39...` baseline;
+the explicit instruction and exact override above explain the discrepancy. The
+checked-in gitlink and The Boss integration/payload revision manifests record the
+consumed revision. No other dependency or SurrealDB baseline changes here.
+
+The new source retains liter-llm version 2.1.1, preserves `schemas/providers.json`,
+and updates `schemas/catalog.json`. The Boss must pin the new catalog checksum and
+the same fork revision used by its UAR payload. Source selection and copied skills
+are not compilation, inference or installer acceptance evidence; those belong to
+the completed application build and actual operation boundary.
+
+### Same release — preserve UAR's explicit host transport boundary
+
+The actual UAR release compilation against `12a2fae...` exposed removed
+`redact_base_url` and proxy/redirect policy APIs used by its credential boundary.
+The fork repair `GQAdonis/liter-llm@1bacb4adc47ba9fa262e1edec6c2f32c4f4649ba`
+on `codex/uar-host-transport-boundary` restores that explicit compatibility;
+PR: https://github.com/GQAdonis/liter-llm/pull/2. This exact source supersedes the
+`12a2fae...` selection above for both the UAR and mini consumers in this release.
+Its catalog bytes are unchanged from `12a2fae...`. Operator-owned `versions.toml`
+remains untouched and this accepted source override remains explicit.
+
+Previously published native CLI artifacts retain their actual source revision
+until replacement artifacts are built and published. Advancing this source
+gitlink must not relabel those existing artifacts as compiled from the repair.
+The observed compilation failure is the reason for the compatibility update;
+this mini change does not claim a successful rebuilt application or operation.
+
+The native release build then exposed one `ClientConfig` builder constructor
+missing the restored transport-policy field. The same fork PR's final repair
+`0617979022aea621dd13541dee07ad84ffcf7d21` initializes that field and supersedes
+`1bacb4a...` as the exact mini/UAR source selection. Skill and catalog bytes are
+unchanged; their payload is regenerated by the next actual application build.