Pin latest liter-llm with UAR transport boundary compatibility - #17
Conversation
Record the operator-requested exact source override without changing operator-owned versions.toml. Assisted-by: Codex:GPT-6 [git, apply_patch]
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7e65d26d25
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| **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 |
There was a problem hiding this comment.
Do not land the new gitlink until the operator-authored pin is updated to match: at this commit, node --test rules/test/versions-toml.test.mjs reports tools/liter-llm: versions.toml pins 4f25d39..., HEAD has 12a2fae.... Treating the prose override as sufficient leaves the repository's dependency authority and doctor/release validation inconsistent; retain the prior gitlink or obtain the matching versions.toml update.
AGENTS.md reference: AGENTS.md:L8-L8
Useful? React with 👍 / 👎.
| ## 2026-09-30 — The Boss consumes the latest committed liter-llm fork | ||
|
|
||
| **Operator instruction:** update liter-llm and prometheus-skills-mini submodule links to |
There was a problem hiding this comment.
Add an Assisted-by: AGENT:MODEL [tools] trailer to the commit message. The author is Codex and this patch adds meaningful generated decision content, but the raw commit message contains no attribution trailer, leaving the repository's required certification metadata absent.
AGENTS.md reference: AGENTS.md:L28-L28
Useful? React with 👍 / 👎.
Keep mini and UAR source consumers aligned without relabeling existing native artifacts. Assisted-by: Codex:GPT-6 [git, apply_patch]
GQAdonis
changed the title
Record the observed native build correction without changing skill or catalog bytes. Assisted-by: Codex:GPT-6 [git, apply_patch]
…payload Copy the complete frozen creator 1.3.0 and cadence 1.1.2 shared payloads from full-pack 1ddcc8b, including emitted runtime modules, schema provenance, assets and per-file distribution receipts. Preserve other skills and current tool pins. Assisted-by: AGENT:GPT-6 Astra [Codex]
1 participant
The Boss's next build needs the latest committed mini skills and liter-llm fork with its UAR host transport compatibility repair. Pin
tools/liter-llmtoGQAdonis/liter-llm@0617979022aea621dd13541dee07ad84ffcf7d21, preserving the current mini main's 100 skills and their executable dependencies.Record the operator's exact requested dependency override in
.prometheus/decisions.md; leave operator-ownedversions.tomlintact. The fork remains version 2.1.1; its provider schema is unchanged and its model catalog has advanced. The Boss release manifests must record the new source and catalog checksums. Existing native artifacts retain their actual older source revision until replacement artifacts are published.The actual UAR release compile exposed removed URL-redaction and proxy/redirect policy APIs at its credential boundary. liter-llm PR #2 restores that compatibility; this exact gitlink aligns mini with the UAR consumer.
No test suites or standalone builds were run. The Boss skill synchronization and runtime materialization completed; compilation and functional operation belong to the actual next application packaging boundary.
The native build also exposed a typed ClientConfig constructor missing the restored field; the final pinned revision initializes it. Skill/catalog bytes remain unchanged.