Release notes¶
Last reviewed: 23 July 2026.
These notes summarize user-visible changes merged to the Threadory product. Deployment to a particular environment may follow later. Use the integration matrix for each connector's status, authorization mode and production usage.
23 July 2026 — documentation and in-product help¶
- A bilingual English/Russian documentation portal now provides task-oriented user, administrator, developer, and reference guides.
- The public portal is packaged as a container; protected operator content is built separately for authenticated GitLab Pages.
- Onboarding, Connectors, Approvals, Reports, Graph Health, MCP, and role settings now open the relevant public guide in a separate tab.
- Connector guides state least-privilege access, external identity, sync direction, expected entities, delivery mode, result checks, and safe disconnection.
- Administrator guides now distinguish reversible configuration recovery from actions that cannot be rolled back, such as published external comments, incurred spend, or retention deletion.
Engineering references: !679, !683, !684, !685, and !686.
21–22 July 2026 — graph trust and actionability¶
- Retrieval results carry path, hop, score-channel, and freshness context so answers and evaluations can explain why evidence was selected.
- Approvals and review output show linked tickets, pull requests, and decisions.
- Graph Health reports relationship coverage, stale sources, missing embeddings, and actionable recommendations.
- Low ticket coverage links to unfiled action items in Reports, where supported items can be filed in bulk.
- API keys support fine-grained MCP scopes, and denied scope checks are audited.
- Person and assignee resolution connects meeting ownership to native tracker identities.
- Connector index policies distinguish deep, shallow, pointer, and excluded content to control retrieval depth, cost, and privacy.
- Ask can combine indexed knowledge with bounded live Slack search while preserving project isolation.
16–23 June 2026 — closed loop and quality measurement¶
- Approved action items can create real GitLab issues and link the issue back to the source work; closing a linked issue can close the action item.
- Meeting content can be organized into cross-meeting topics and a navigable taxonomy.
- Review evaluation captures automated scores and human outcomes for regression testing.
- Cost reporting attributes supported usage to people, skills, models, background actors, and time.
Detailed change history¶
The repository's human-maintained CHANGELOG.md is the detailed weekly
engineering log and includes MR references and operational evidence. It may
require repository access. Release notes intentionally omit package-level and
internal-only changes.