[currentbits]

Version 0.8.0: the new app layout (#420), What I noticed and drafting quiet checks (#421), and the context estimate (#422).

• Bumps the workspace version to 0.8.0 and renames the changelog's Unreleased section, adding the entries App UI: bots-first sidebar, chat bubbles, everything else opens over the chat #420 and Show what tools and memory take of the context; warn when Ollama's window is too small #422 didn't write.
• Also brings in one commit that was only on the local master: skill fixes warn when they drop a rule, and say when the skill is one you chose (crates/mimir-core/src/db/skills.rs, with its test).

Checks: cargo test -p mimir-core --lib (327 passed).

After merging: tag v0.8.0, let release.yml draft the installers, notarize the Mac app locally, publish.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-11T19:10:40.288355Z	6876339	PR opened

ℹ️ 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" or "@codex security review".

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]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 68763395f5

ℹ️ 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".

[chatgpt-codex-connector]

Preserve chosen-skill provenance across renamed merges

When a saved or library skill is merged into a skill with a different name, subsequent fixes lose the “You chose” notice. skill_merge_propose allows the merged skill to have a new name and records its source IDs in replaces, but this query only checks historical rows with the current name. For example, merging a library skill “Pay safely” into “Pay invoices”, accepting it, and then patching “Pay invoices” produces no notice even though it incorporates a skill the user explicitly chose. Follow the merge ancestry (or persist the chosen provenance) so this approval context survives accepted merges.

Useful? React with 👍 / 👎.