Added a new API reference partial (_surveys.html.haml) that documents Surveys endpoints, parameters and responses. Change was released to production on Jan 16, 2026. Impact: provides authoritative, in-repo documentation to help developers integrate with and maintain the Surveys API.

Fixes bug in issue_browse where the 'All Time' group was rendered twice instead of 'All Time' followed by a 'Per Interval' grouping. Updated the view rendering and adjusted the integration test (test/integration/issue_browse_test.rb) to assert correct ordering and labels. Result: correct grouping in the UI and regression coverage to prevent recurrence.

Fixes Copilot 403 token handling by adding retry windows, tolerating partial auth failures, and improving logging to surface 403 responses. Adds scaffolding for GitLab Issues (ExternalIssue::GitlabIssue and Gitlab_issue_tracker_integration) to seed future issue sync. Related to IN-497. Impact: reduces transient Copilot auth interruptions and provides a foundation for GitLab issue synchronization.

Update derive_series_segments in app/lib/presenters/concerns/ai_segment_concerns.rb to enforce an ascending sort of cohort series by usage (Least use → Most use). Multiple additions and small updates replace the prior ordering behavior so series are calculated and ordered deterministically. Impact: cohort charts now consistently present segments from least- to most-used, improving readability and analysis.

Update vendor/gems/gitclear_teams/app/models/team_repo.rb (ensure_cached_stat_rebuild_on_create_destroy) to enqueue a build of LLM usage metrics when a Team is created and may have LlmUsageMetrics. This schedules metric generation asynchronously on create (consistent with destroy handling), preventing missed initial LLM stats and improving accuracy of LLM usage reporting.

Return audit PRs based on the most-recent "merged_at" value when a closed-date filter is provided, and add new audit fields (business_minutes_awaited_first_review, business_minutes_cycle_time, business_minutes_lead_time, business_minutes_open_to_closed, first_commented_at, first_commit_authored_at, post_merge_delta, squash_commit_sha). Changes touch V1::AuditsController and PullRequestConcerns::PullRequestJsonConcerns so API audit responses and closed-date queries are more accurate for report...

Adjust app/jobs/assign_pull_request_post_merge_commit_work.rb to search for and handle commit-message lines that indicate updates to squashed PR commits, with a small test tweak in test/unit/pull_request_post_merge_commit_test.rb. This fixes the failing test and ensures post-merge commit assignment correctly recognizes squashed-PR update lines so ownership is assigned reliably.

Return early from RepoImportProgress#calculate_percent_complete (app/models/repo_import_progress.rb) when the default branch has been processed as far back as the repository's processing epoch. This prevents unnecessary scanning/aggregation, fixes potential over-reporting, and reduces CPU/I/O during import progress calculation for more efficient, correct percent reporting.

Add an early-out to RepoImportProgress#calculate_percent_complete (app/models/repo_import_progress.rb) so that if the default branch has been processed as far back as the repository's provider_created_at the calculation returns immediately. This avoids scanning older history, prevents overcounting and wasted work, and improves import progress accuracy and performance.

Replace timeOffHtml with a timeOffArray: move derive_time_off_array out of vendor/gems/commit_activity_browser/app/lib/bubble_committer_concern.rb into app/javascript/bundles/cab-viewer/cab-committers-frame.js and update committer tooltip/content to consume the array. Prevents HTML-escaping problems in CAB and ensures correct time-off rendering.

Fixes a bug where the PR comment fallback time used 30.seconds without dividing by 1.minute, producing implausible minute estimates that propagated to PullRequestReviewer. Updated the calculation in code_comment_extra (with unit test adjustments) so minutes are computed correctly, restoring realistic comment-time estimates and preventing inaccurate reviewer timing metrics.

Add a sparkline to the committer avatar hover (updated in app/javascript/bundles/cab-viewer/cab-committers-frame.js). renderSparkline and tooltip markup were extended to render a 12‑month delta mini-chart inside the hovercard, giving reviewers a compact visual of recent committer activity for faster context.

Update lib/tasks/whenever/pull_requests.rake to queue DiscoverPr jobs more frequently during a repository's early existence since the initial DiscoverPr job now limits scans to main branch plus a buffer. Also sort and reorganize subscription logic (Defines::Subscription and the subscribe_manager Subscription model), adding/adjusting refresh interval behavior. Result: better initial PR coverage for new repos and clearer subscription definitions.

Update RepoReleaseRule to enqueue PR discovery immediately for rules that match pull requests. Added a pull_request_rule? predicate and modified after_create_rule to manually queue discovery when appropriate. This ensures new PR-focused release rules find matching PRs right away instead of waiting for the next scheduled sweep, improving release responsiveness.

Expose an aggregate_by parameter on the Reports API by updating the API definitions and V1::ReportsController to accept and forward aggregate_by for report queries; minor related model and test tweaks included. Clients can now request aggregated reports by a specified dimension, improving reporting flexibility.

Adds a v1 public API endpoint (POST /api/v1/ai_usage) to receive AI usage statistics and includes an integration test (vendor/gems/customer_api/test/integration/api_ai_usage_test.rb). Deployed to production on Oct 22, 2025. Enables clients to submit usage telemetry for improved monitoring, reporting and billing.

Introduce periodic reprocessing for releases and add hooks to periodically refresh defects and issues. Refactored PopulateReleasesFromRule job and added a new releases.rake task in the release_track gem to drive scheduling. Active trials receive higher-frequency refreshes, and cached ResourceTeamStats are only updated for entities with an active subscription. Reduces stale data and avoids unnecessary cache churn.