Release Notes

Requirements Browser and Delivery Status

• CR-428 — Bulk Delivery Status updates: the multi-selection banner now lets users assign a status of a chosen type to selected Requirements. Inherited Requirements are skipped without auto-forking. In MERGED and ARCHIVED branches, the server returns 409 BRANCH_READ_ONLY while preserving the dialog and selection. Successful operation results appear after the banner closes, including when every selected item was skipped
• CR-427 — Module Delivery Status summary: when Requirements are grouped by status, each module shows a progress bar with the distribution of Requirements by Delivery Status
• CR-422 — Delivery Status for Requirements: statuses are assigned to individual Requirement revisions. The browser provides separate filters and optional columns for status types, while Requirement details include Delivery Status parameters. Creating a new revision resets each assignment to the type's default status or leaves it unset
• CR-420 and CR-421 — Delivery Status settings: project settings now support creating and ordering status types and their statuses, with an optional default status for each type. These settings are included in project import and export format v3
• CR-373 — Bulk Requirement moves: added a Move action to the multi-selection menu for Requirements within a module, using the existing flow for moving Requirements between modules
• CR-418 — Configurable table columns: supported browser tables now define required and configurable columns with ordering controls. After Apply, the backend prepares data for optional columns only when they are enabled in the active configuration, while always retaining required fields

AI Assistants, MCP, and automation

• CR-426 — Deprecated data in MCP: detailed MCP responses for Data Entities now exclude attributes and values marked as deprecated
• CR-396 and CR-425 — AI preset catalog and assistant restrictions: updated the active Principal, Senior, Middle, and Junior presets and the models available to each assistant. Luna is excluded from the options for the affected assistants while remaining in the general catalog. Older presets are marked as deprecated, with a runtime fallback defined for saved legacy settings
• CR-379 — GPT-6 Astra: added Astra to the AI model catalog with max, xhigh, and high reasoning levels, and aligned catalog ordering and available presets across workflows
• CR-413 — Finding authorship and MCP origin: Finding details and related contracts now include authorship information and an indicator of MCP origin
• CR-412 — Architecture Role in AI workflows: clarified how AI Unit Discovery and AI Subsystem Architect use Architecture Role in their contracts and prompt workflows
• CR-407 — Personal MCP token: introduced a single user-level MCP token in place of tokens tied to membership in individual projects
• CR-395 — Additional Requirement validation in AI Test Designer: an unresolved additional Requirement reference in a step now produces a non-blocking warning. The original key is retained for diagnostics, and the step can be applied without the relationship. An invalid primary Requirement reference remains a blocking error
• CR-354 — Alignment Verifier from specifications: added a dedicated verification action in detail views and multi-selection menus for Requirements, Data Entities, User Interfaces, and API Operations, including a preview and start dialog
• CR-356 — Guidelines Verifier from specifications: added a dedicated Unit Guidelines Verifier action for the same specification types, with corresponding menu entries and a preview and start flow
• CR-353 — Findings in AI Analyst context: selecting a Change Request now adds a brief list of its related Findings to the initial context. Full Finding data remains available through the artifact-loading tool
• CR-352 — AI Product Expert intermediate results: the “Intermediate results received” message is now hidden in AI Product Expert responses; other assistants retain their existing behavior
• CR-359 — AI Product Expert references: extended the references contract with the data needed to display and open artifact cards. Tasks displayed in a window open artifacts in a modal, while tasks on a standalone route use a drawer
• CR-357 — Source Code files in AI Product Expert: resolved implementation-file references in the Source Code section are now clickable and open File Detail. Unresolved references remain visible but inactive

Units, architecture, and diagrams

• CR-411 — Architecture Role for Software Units: Unit Types now have a role that distinguishes runtime, test, and supporting Units. The role is used in the browser, specification relationships, and verification workflows
• CR-380 — Diagram in Units Browser: the diagram uses the selected scope to display Units, technical dependencies, and related User Interfaces and API Operations. Relationships do not represent actual data flow
• CR-381 — Create Domains from Units Browser: added a Domain creation button to the navigator. It opens the editor and selects the new Domain as the current scope after saving
• CR-382 — Units diagram limit: introduced a server-side limit of 200 nodes by default for the final graph. When the limit is exceeded, a message is returned instead of the diagram
• CR-384 — List and Diagram views for Requirement Units: the Requirement Code tab now offers a List/Diagram switch and fullscreen diagram viewing, with data loaded in the appropriate branch context
• CR-408 — Diagram highlighting: defined highlighting for the active node and its dependencies in supported diagrams
• CR-409 — External Units in diagrams: clarified how external Units and dependency chains appear in Units Browser and the diagram on the Requirement Code tab

QA and test management

• CR-429 — Revision numbers in QA MCP: Test Result resources and tools now use sequential Test Case revision numbers instead of internal revision IDs, including in nested results
• CR-406 — QA MCP MVP: defined the initial QA MCP scope, covering a personal token, QA resources, and tools for creating and updating Test Results, with corresponding account and QA Dashboard contracts
• CR-424 — Automatically flag suspicious Test Results: after a commit import, the system follows the chain from changed files through Software Units, Requirements, and Test Cases to flag affected historical Test Results as suspicious. This applies only to imports into a Code Branch mapped to Main
• CR-405 — Environment in Test Run reports: Test Run reports now include information about the test environment associated with the run
• CR-403 — Edit Test Run descriptions: descriptions are edited through a dedicated action, with Save to commit the change and Cancel to discard it
• CR-355 — Delete related Test Cases: deleting a Requirement also soft-deletes its active direct Test Cases in the same branch. Bulk deletion retains a separate transaction boundary for each Requirement

Activity logs

• CR-385 — Shared activity log model: aligned one-off and accumulated events, branch and revision context, and a reusable log viewer for supported artifacts
• CR-388 — One relationship event for both participants: artifact relationships are recorded as a single event with two participants. The event appears in both participants' logs and only once in the project-wide log
• CR-389 — Subsystem activity log: added history for Subsystem and related Unit Type changes, including lifecycle events, moves, and bulk operations
• CR-392 — Issue activity log: added an Issue log tab covering changes, lifecycle events, and relationships
• CR-393 — Change Request activity log: added a tab in Change Request details covering core changes, relationships, file operations, and bulk operations
• CR-397 — Milestone activity log: added a log for field and period changes, lifecycle events, and relationships with Issues and Test Runs
• CR-398 — Test Case activity log: added a tab in Test Case details covering changes to the case and its steps, including lifecycle events and bulk operations
• CR-404 — Test Run activity log: added a Test Run log tab and recording of core lifecycle events, changes to the set of Test Cases, archiving, restoration, and deletion

Dashboards and project overview

• CR-399 — Subsystem General tab: added an overview with Specs, Implementation, and Quality metrics. Quality is available when the Main Branch conditions are met and test management is enabled
• CR-400 — Subsystem cards on Project Dashboard: cards now show the total number of Findings with a breakdown by severity, the latest commit, and SYNCED progress
• CR-401 — Latest commit in Subsystem General: added the latest commit to the Implementation section, and made overview sections independently collapsible
• CR-402 — Specifications and QA progress: Specifications now includes a section description, a lifecycle progress bar, and a current Findings count. The Test Cases card shows Requirement coverage, including outdated coverage and uncovered Requirements

Issues, Change Requests, and workflow

• CR-423 — Combined workflow and resolution settings: status, transition, and available resolution settings are now managed in one form and saved together. A client-side action can enable all transitions at once
• CR-378 — Bulk Change Request status updates: added Set Status to the selection banner for active Change Requests. The existing Close action is unchanged
• CR-377 — Change Requests table: Key, Status, and Name are now separate required columns, while Project Branch is a separate configurable column
• CR-371 — Configurable Change Request statuses: added status configuration, ordering, colors, and catalog import and export for the ACTIVE and CLOSED groups
• CR-367 and CR-370 — Draft and canceled AI Tasks in Change Requests: Draft and Canceled tasks are hidden from the related AI Tasks list. A task in Draft does not update last activity or prevent branch changes; these effects begin when the task starts
• CR-360 — Related Issue data: Change Request details and the operation for changing the Issue relationship now return a consistent Issue summary with its type, priority, and status
• CR-358 — Issues in Module details: added a read-only tab listing related Issues and Requirement keys, with the Issue status displayed first
• CR-394 — Open Change Requests in their branch context: on a standalone route, a branch mismatch offers navigation to the Change Request's branch. In drawers and modals, dependent data loads in the Change Request's branch context
• CR-387 — Change Subsystem identifiers: replaced inline editing with a modal that displays the current and new keys and warns about the consequences of changing the ident

Specifications, UI, and files

• CR-416 — Diagram in User Interface details: added a Diagram tab with a dedicated contract for loading the path diagram
• CR-414 — Preview in User Interfaces Browser: added a configurable Preview column with corresponding list and metadata contracts
• CR-417 — Figma wireframe creation: temporarily removed the entry point for adding Figma wireframes. Previously created Figma wireframes remain available for viewing
• CR-419 — API Operation Type and Technical Name: General now displays Type and Technical Name in API Operation details. Type also remains available in Params
• CR-386 — AI result editor modes: added Diff, Side by side, and Editor modes for AI Analyst, AI Subsystem Architect, and AI Test Designer, with Diff selected initially
• CR-390 — Data Entity description diffs: attribute and value descriptions now show inline differences between the original and proposed text
• CR-391 — Consistent folder contract: unified folder_path and folder structure handling for supported artifacts, and clarified naming rules for unambiguous path parsing
• CR-410 — Requirement Markdown export: module exports now exclude deleted Requirements and their related artifacts
• CR-365 — Markdown export for Data Entities and API Operations: added export of selected artifacts from the multi-selection menu, with a simple filename dialog
• CR-369 — Export from artifact details: added single-artifact Markdown export of the current version to the detail menus for Data Entities and API Operations
• CR-366 and CR-368 — Paste images into the editor: clipboard images are first uploaded as files attached to a supported artifact and inserted only after a successful upload, using the returned insert_url. Original data, blob, and external URLs are not saved

Integrations and tenant management

• CR-415 — Gitea integration: added integration setup, token management, and push webhook handling with signature validation in the tenant context
• CR-372 — Tenant API and Sales Backend: aligned tenant status and deployment contracts, including provisioning_id, create-only behavior, and a conflict response when the tenant already exists
• CR-364 — Initial AI credit balance: added an optional initial_ai_balance field to the deployment contract, defaulting to 0 when omitted
• CR-362 — Protected Initial Setup: the initial setup screen now uses a link containing a token and email. The email is prefilled and cannot be edited, and the server validates the token
• CR-361 — Codex handoff: added external Codex handoff entries to the Change Request menu for affected Subsystems, using the repository URL and the corresponding branch context
• CR-363 — Localized handoff text: handoff text now follows the locale in the user's profile

Branching, deletion, and recovery

• CR-375 — Merge branches into Main: designed a complete merge flow for active branches, including preview, conflict analysis, a choice of Main or Branch, stale-preview protection, and atomic application. Test Cases remain bundled with their Requirement
• CR-376 — Deleted artifact views: versioned artifacts display their last revision before deletion with a banner, while non-versioned artifacts show a dedicated deleted-artifact state
• CR-383 — Restore deleted artifacts: clarified Rollback flows for versioned artifacts and Recovery for Findings. Finding recovery removes the soft-delete flag without changing its data, relationships, or lifecycle status

Implementation Dashboard, billing, and platform

• CR-351 — Compact domain verification progress: the Domains section now shows only segmented progress bars, with tooltips identifying each state and its percentage. The detailed breakdown has been removed without changing the API
• CR-326 — Read-only domain verification summary: added aggregate verification metrics for domains without drill-down
• CR-275 — Core Implementation Dashboard metrics: added minimal SYNCED and verification indicators for each subsystem
• CR-342 — Dedicated deployment error state: aligned DEPLOY_ERROR handling across the API, tenant context, pre-login checks, and frontend. Unavailable deployments now have a distinct state with a Retry action
• CR-340 — Tenant licensing and deployment management: added a module covering the Deployer API, license parameters, AI credit balances, and local billing
• CR-341 — Automatic verifier task archiving: verifier AI Tasks can now be archived on a schedule after a configured number of days
• CR-312 — Billing in instance settings: added a Billing section with an AI credit summary

AI Product Expert, AI Tasks, and assistants

• CR-350 — Finalized AI Product Expert answer panel: the answer panel is shown only after the result has been finalized; while processing is in progress, user, tool, and progress messages retain their standard order
• CR-349 — Separate AI Product Expert follow-up answers: every follow-up now creates its own answer card with Details, References, Source Code, and Actions sections, while earlier answers remain in the conversation history
• CR-348 — AI assistants in Finding details: added an AI menu with AI Analyst, AI Subsystem Architect, and AI Product Expert; the current Finding is passed into the task context
• CR-345 — Create a Change Request after Apply: a new Change Request can now be created directly from the AI Task attachment flow after applying a result
• CR-344 — Link applied AI Analyst tasks to Change Requests: added confirmed attach and detach actions with synchronization of revisions and subsystems
• CR-343 — Review AI Test Designer changes: results can now open a Test Case and compare its previous and new revisions in a drawer or modal
• CR-317 — Trace applied AI Task changes: relationships to changed artifacts and applied revisions are preserved and available in AI Task, Change Request, and revision details
• CR-324 — Withdraw proposed artifacts: new artifacts proposed by AI Analyst can be marked as withdrawn; withdrawn items are hidden and excluded from Apply
• CR-311 — Consistent AI Assistant contracts: synchronized the shared rules for prompts, schemas, validation, and relationship handling
• CR-302 — AI Tasks naming and links: renamed AI Session Summaries to AI Tasks and added links that open task details in a modal
• CR-299 — Assistant selection for quick tasks: added an assistant picker when quickly starting an AI Task
• CR-298 — Simplified global search: search mode is now selected automatically, with AI Product Expert used as a fallback when no results are found
• CR-297 — Draft submission shortcut: AI Task Drafts can now be submitted with Ctrl/Cmd+Enter
• CR-294 — Open AI Task details in a new tab: task details opened from draft and quick-create flows now support new-tab navigation
• CR-283 — Focused AI Assistant navigation: verifier assistants are hidden from the AI Assistants list in the left navigation
• CR-282 — Flex service tier: manual AI Task runs can now use the flex service tier
• CR-274 — Applied task notification cleanup: unread-update indicators are hidden for applied AI Tasks
• CR-272 — In-modal task progress: progress is displayed directly in the modal after an AI Task starts
• CR-278 — Partial result publication: refined partial execution_result_updated publication and the presentation of updates in the timeline
• CR-277 — Intermediate task updates: synchronized partial-publish requirements with timeline behavior for intermediate AI Task results
• CR-284 — Cleaner proposed-artifact timeline: removed redundant status tags from new artifacts in the AI Task timeline
• CR-263 — Updated intermediate-result message: revised the message shown after a tool call produces an intermediate result
• CR-262 — Revised partial-result messaging: reworked the logic for showing partial-result messages after tool calls
• CR-258 — Clearer partial AI Task results: refined how partial results are displayed
• CR-261 — Scheduled verifier tasks: clarified verifier-task scheduling through AI Automations Runtime, together with processing and billing rules
• CR-257 — Clarification mode after Restart: restarting a task now preserves CLARIFICATION mode
• CR-259 — Expanded AI credit accounting: usage accounting now includes cache_write_tokens and web search
• CR-300 — Combined Requirement changes: a single Requirement item can now deprecate the artifact and modify its relationships at the same time
• CR-267 — Explicit artifact types for AI Analyst: the AI Analyst contract now passes artifact types explicitly
• CR-264 — Revision rollback availability: revision details now include can_rollback so the interface can show the rollback action only when available
• CR-276 — Continued clarification conversations: CLARIFICATION mode now supports continuing the conversation after answers are provided and then proceeding with execution

Findings, MCP, and traceability

• CR-347 — Batch Finding resolution through MCP: the solve-finding tool accepts multiple Finding keys, returns per-item results, and supports partial success and idempotent confirmation
• CR-346 — Finding creation through MCP: added the create-finding tool with links to artifacts, Software Units, and a Change Request, plus deduplication and origin metadata
• CR-331 — Related items in MCP module resources: module resources now include compact lists of related requirements and specifications
• CR-330 — Related requirements in MCP artifact resources: Requirement, Data Entity, User Interface, and API Operation resources now include compact lists of related requirements
• CR-315 — Richer MCP relationship context: MCP contracts now include compact related_units data and additional Requirement relationships
• CR-314 — Leaner MCP app manifest: removed tenant, branch, and code branch data, and clarified trace-file fallback behavior and valid empty results
• CR-270 — App manifest tool: app manifest retrieval is now also available through get-app-manifest, and the deprecated Prompts flow has been removed
• CR-268 — Restore missing Requirement relationships: links in a Requirement description can now be used to manually create relationships that are not yet recorded
• CR-280 — Code tab in Change Requests: added related Software Units for affected specifications
• CR-316 — Subsystem context in specification commits: commit lists now identify the subsystem
• CR-256 — Code tabs for specification artifacts: added a Code tab to Requirement, Data Entity, User Interface, and API Operation details
• CR-255 — Commits in Code tabs: added a Commits section to artifact Code tabs
• CR-279 — Clearer Requirement relationship label: renamed Included / Depends on relationships to Related Requirements
• CR-286 — Consistent editor mentions: standardized the mention format for users and artifact links in the WYSIWYG editor
• CR-281 — Link insertion shortcut: links can now be inserted in the WYSIWYG editor with Ctrl/Cmd+K without losing focus
• CR-265 — Expanded AI Unit Alignment results: the contract now covers Requirement and User Interface results, relationship statuses, and Findings
• CR-266 — API tab in subsystem details: added API Surfaces and Operation Types
• CR-307 — Richer AI Unit Alignment context: added unit_type and file paths for dependencies and consumers
• CR-306 — Refined AI Unit Alignment contract: clarified initial context, tools, semantic validation, verifier metadata, and the scope of Findings

Implementation, Units, and Files

• CR-339 — File cleanup when deleting Units: related files are detached and their Unit Sync state is reset to UNKNOWN for both individual and bulk deletion
• CR-338 — Source Code tab for Implementation Files: added a lazy-loaded, read-only source viewer with empty and error states and a Retry action
• CR-337 — More precise Unit Discovery: discovery now focuses on input files, considers only confirmed composite files, and rebuilds dependencies and consumers for affected Units
• CR-336 — Subsystem filtering in Units Browser: added a multi-select Subsystem filter
• CR-333 — Fresh file-to-Unit mappings during Apply: Apply uses the latest confirmed association within a configurable time window to prevent duplicate Units
• CR-334 — Branch-aware Unit restoration: deleting a Unit clears the files' unit_id; restoring it refreshes relationships in the correct branch context
• CR-335 — Updated Implementation navigation: Implementation Files now appear immediately after Units, while Commits has moved to the end of the section
• CR-332 — Cross-domain Unit Discovery fallback: discovery can match Units by name, type, and normalized file path regardless of domain
• CR-329 — Domain sorting and actions: added domain sorting and permission-aware hover action menus in Units Browser
• CR-328 — Change domains for locked Units: locked Units can now change domains through Draft creation, with a preflight check and rollback on failure
• CR-327 — Reusable deleted domain keys: a deleted Unit Domain key can be reused, while uniqueness remains enforced across active project domains
• CR-325 — Canonical Unit Domain keys: domains now have immutable canonical keys, Unit Discovery uses those keys, and names for new domains are generated automatically
• CR-318 — Sync status in Unit File Paths: added a synchronization status tag beside file information
• CR-323 — Shared Browser Family interactions: added Cmd/Ctrl-click multi-selection across all supported browsers
• CR-322 — Recovery for stuck file synchronization: files left in SYNCING can now be recovered to FAILED automatically or manually
• CR-321 — Draft artifact auto-close rules: formalized behavior across artifact types, branches, inherited states, schedules, and concurrent changes
• CR-320 — Unit synchronization API contracts: clarified unit_sync_state, related Units in detail responses, and file relationship contracts
• CR-319 — AI Unit Discovery Apply rules: refined Apply behavior and the discovery prompt
• CR-310 — More Units Browser columns: added configurable Subsystem and File Paths columns
• CR-308 — Linear Unit Domains: replaced hierarchical Unit folders with flat domains and updated browser, detail, branching, chooser, and AI Discovery flows
• CR-309 — Dedicated Unit detail screen: Unit details now have a standalone screen with drawer and fullscreen modes
• CR-305 — Duplicate Unit validation: Unit creation now checks for an existing Unit with the same name in the relevant folder
• CR-304 — Configurable Units Browser columns: users can choose which columns are displayed
• CR-303 — Verification filters in Units Browser: added verification-status filters and clarified deleted-state Unit behavior
• CR-301 — Not Synced Files Browser mode: added a view dedicated to files that are not synchronized
• CR-313 — Ignored Files Browser mode: added a view for ignored files and an action to remove manual ignore status
• CR-296 — Attach files to locked Units: the chooser now permits file attachment to locked Units
• CR-295 — Detach files from locked Units: detaching a file moves the Unit to Draft through the standard workflow
• CR-293 — Manage file links in Relations: added actions to detach a file from a Software Unit or reassign it to another Unit
• CR-269 — Expanded Unit list data: UnitListItem now includes the fields required by the frontend to present Unit and branch state
• CR-273 — Unit Discovery grouping: manual discovery runs now include a file-grouping mode selector

Milestones, Issues, and other UI updates

• CR-292 — Milestone parameters tab: parameters now follow the shared detail-view pattern and appear in a separate tab in the narrow drawer
• CR-291 — Improved Milestone overview: reworked the description, inline editing, and Progress presentation in General
• CR-290 — Updated Milestone details: removed the previous description block and refined the Issues and QA tabs
• CR-289 — Expanded Milestones Browser: added new columns and QA Progress
• CR-288 — Milestone permissions and actions: clarified authorization, bulk deletion, and navigation to QA entities
• CR-287 — Complete Milestones section: specified browsers, details, lifecycle actions, bulk operations, permissions, and QA integration
• CR-285 — Quick Issue status changes: duplicated the status control in the Params block for faster switching
• CR-260 — Subsystem name validation: added validation and automatic format conversion while entering a subsystem name
• CR-271 — Create modules during bulk moves: the bulk Move Requirements flow can now create a new module

Change Requests and AI Tasks

• CR-252 — AI actions for multiple selected Change Requests: added a dedicated AI menu with AI Product Expert and AI Analyst actions to the row-selection banner. The menu is available to any user who can view Change Requests in active or archived scopes. Selected CR-* items are passed only as the initial context for a new draft AI Task, which opens in a quick modal without changing the route. Starting AI Analyst from a bulk selection does not link the task to any individual Change Request
• CR-246 — Applied state and filtering of related AI Tasks: separated the persistent AI Task.is_result_applied flag from the task lifecycle status. All related tasks remain visible in Change Request details, while their Applied state is determined by this flag. Model-facing and MCP representations include AI Analyst summaries only for tasks whose results were actually applied, without falling back to execution_result.applied

MCP and Change Request context

• CR-249 — Simplified MCP Change Request resource: focused the MCP response on the change context: Change Request data, affected artifacts, additional project instructions, and summaries of related AI sessions. The generated implementation workflow has been removed from the resource payload and remains the responsibility of the implement-change-request prompt
• CR-250 — Affected Requirement URIs in MCP: added resource URIs to affected artifacts, allowing MCP clients to navigate from a Change Request to the full specification of an affected artifact in the current branch context
• CR-251 — Full folder paths for affected artifacts: added a folder field containing the complete folder_path, including parent folders. This gives AI tools and external MCP clients clearer Change Request context without exposing technical folder keys

AI Assistants and user interface

• CR-254 — Findings in AI Assistant context: added support for FINDING-* references in draft AI Task creation and editing, the assistant catalog, model-facing context, and the search_artifacts and load_artifacts tools. A Finding Chooser now uses the existing Findings API, and Finding Solution Action can open an AI Analyst draft with the current Finding and its related artifacts in the initial context
• CR-253 — Resolved Change Request references in AI Product Expert: synchronized AI Product Expert structured results, prompts, schemas, validation, detail and updates APIs, and the result area for CHANGE_REQUEST references. A resolved CR-* reference now appears by name in the Change Requests group and opens its detail route; deleted, inaccessible, or unresolved Change Requests retain an explicit key-based fallback
• CR-248 — AI Assistants group order: standardized the project sidebar order so that New Task appears first, followed by Tasks, with the recent task list displayed below a separator

Specification visualization

• CR-247 — Spaced Detailed mode for Data Entity diagrams: auto-layout now accounts for the actual dimensions of attribute cards, prevents overlaps, and maintains at least 48 px between card boundaries in both the Diagram tab and the fullscreen popup

MCP and AI integrations

• CR-241 — MCP resources, prompts, and transport rules: refined the contracts for the MCP Server, MCP tokens, and tool trace files; added or updated MCP resource modules and resources for units, artifacts, Change Requests, and app manifests; formalized MCP Resource Templates, MCP Prompts, transport rules, and the retrieval of MCP connection parameters for subsystems
• CR-242 — MCP attribute removal: removed the specified attributes from MCP resource modules and individual MCP resource module definitions, narrowing and clarifying the public MCP contract
• CR-229 — Findings in get-artifact: extended the MCP artifact retrieval operation to include Findings and their related context, allowing AI tools to access both an artifact and its verification results
• CR-228 — Partial updates to AI code prompts: added support for partial changes to subsystem.code_ai_prompt and unittype.ai_code_prompt, including AI Subsystem Architect workflows for saving draft items and applying results
• CR-225 — Consistent purpose text for tool calls: standardized first-person purpose messages across AI Analyst, AI Subsystem Architect, and AI Product Expert tools to align progress messages with prompt templates

AI tasks, chat, and AI credits

• CR-236 — Instance-level AI credit accounting: extended AI credit charging to task starts, continuations, reruns, and automatic or manual AI checks; aligned AI Task, AI Task Message, instance settings, AI Model Presets, credit transactions, pricing plans, queues, canonical transcripts, and the AI Task Browser UI
• CR-237 and CR-238 — Consistent AI credit billing: resolved conflicts in charging, refunds, and billing error handling; standardized the use of AI credit transactions and billing error records across task lifecycle, archiving, reruns, and AI Task display
• CR-232 and CR-235 — Separate AI Task result application state: separated result application from the main task status with a dedicated application flag, preserving the original execution status while showing whether the result has been applied
• CR-239 — Route-based AI Task Draft opening: AI Task drafts now open through a route when an AI Assistant type is selected, improving quick task creation and navigation between assistants
• CR-234 — Updated AI Assistant names: renamed AI Assistant navigation items and consolidated separate New Task actions into a single navigation item
• CR-226 — Follow-up with Cmd/Ctrl+Enter: added a keyboard shortcut for sending follow-up messages in AI Task chat
• CR-224 — Progress, web search, and tool calls: unified the display of progress messages, web searches, tool calls, and tool results around a shared tool-call, tool-result, and progress model

Requirements Browser, folders, and Issues

• CR-245 — Required subsystem selection for new Requirements: creating a Requirement now requires at least one subsystem on both the frontend and backend; the rule applies only during creation and does not prevent removing the last subsystem from existing Requirements
• CR-244 — Save folders with Enter: standardized Enter-key submission for creating and editing module, Data Entity, User Interface, API Operation, and Unit folders
• CR-243 — Unified module context menu: aligned module actions across table and detail views in the Requirements Browser, including Requirement creation, module moves, Markdown exports, and deletion
• CR-227 — Configurable active Issue column: added an optional Requirements Browser column showing the active Issue, its status, and its relationship to the Requirement
• CR-222 — Requirements column in the Issues Browser: added an optional column showing linked Requirements in both active and archived Issue views, including metadata and list API support
• CR-221 — Issue details in Change Request parameters: Change Request details now show the selected Issue when an Issue is linked, with corresponding updates to the detail API and Issue relationship operation

Settings and navigation

• CR-240 — Feature toggle visibility in experimental mode: feature toggle visibility now depends on whether experimental mode is enabled in general instance settings and project settings, including Project General Settings retrieval

Findings and quality assurance

• CR-230 — Project-aware Finding numbering: public Finding numbers are now scoped to projects, preventing ambiguous keys and providing the correct Finding context to AI verifiers
• CR-233 — Finding severity group order: Active Findings Browser and table views now show severity groups from highest to lowest priority, starting with High
• CR-231 — Changing the type of locked Units: improved individual and bulk type changes for locked software units, including correct restoration of the Unit status and related Revision when an operation fails
• CR-223 — Results in the QA Dashboard: added a Results section where users can switch Test Environments and review test run results for the selected environment across Requirements, Test Cases, Test Runs, execution results, and environment states

• Updated navigation logic between sections
• Implemented a new AI Analyst that works with all specification types simultaneously
• Revised the Questions Mode workflow and context preparation when switching to execution mode
• Improved AI agent logic for searching across specifications and the codebase
• Added a tabular view for spec–code alignment
• Introduced configurable rules for automating specification and code processing, including warning generation
• Minor UI improvements

• Major update, product renamed to Reqode
• Ability to use AI Assistants from Issues
• Unit Architect AI Assistant added

• AI: Business Requirements writer assistant reworked
• AI: Code writer assistant reworked
• AI: Features (software requirements) writer assistant reworked
• AI: Assistant is able to require artifacts automatically (can be switched on/off)
• AI: Assistant question mode: writes a plan and asks questions before starting a task (can be switched on/off)
• AI: Ability to add context while working with the assistant
• Business Requirements: Bugs fixed, new way to create and view relations
• Issues: Issues sidebar navigation uses requirements tree
• Change Requests: Multiple applications per change request allowed
• Change Requests: Change Request can be linked with artifact revisions
• QA: Test coverage widget now shows coverage by software requirements structure (module folders)
• User Interfaces: Beta implementation of wireframing tool integration in User Interfaces
• Minor UI improvements
• Code: Gitlab integration bugs fixed.
• Issues: Yandex Tracker priority fix

• Quick Verification
• Test Case editor improvements
• Requirement statement as an artifact
• UI minor improvements
• Commit impact on test case runs
• Test case runs suspicious state UI added
• Issue - Requirements relation reworked
• Personal workspace (issues, test cases) bug fixes

• Show artifact revision name when revision is opened (istean of actual name)
• Requirements tracing table open issues assignee fix
• Wysiwyg editor draft cancel (reset) button added
• Wysiwyg editor draft auto recover
• Commit Actions and commits UI improvements
• Issue set reworked (ordering added, improved behavior)
• Re-sync commits button in code → commits section
• Multiple issues related to requirement branches fixed
• Closed baseline functionality improved
• Baseline closed improved
• Package icon removed
• Code highlighting for php/c/js styled source code
• Issues: open context inline (requirement and data entity so far)
• Issues: external sync improvements (bulk action button)
• AI Tasks: Context tab added
• UI minor fixes