improvement(changelog): add meaningful release coverage

[waleedlatif1]

Summary

• Clarify the six published feature announcements and add selected changes from their original releases: file diffs and remembered panel widths, You.com and connected-source browsing, Plane and Buffer actions, and Agent defaults.
• Keep the copy focused on actual product changes, preserve the reviewed media and original publication identities, and update editorial guidance to reject padding and verify release membership.

Type of Change

• Content improvement

Testing

Content audit passed for all six entries. Browser review covered desktop and a real 390px viewport; HTTP review verified all six articles, index/archive, RSS, sitemap, canonical metadata, and all 18 linked destinations. Generated repository artifacts remain in sync. Full repository checks and test suites run in CI; no local test suites were run.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (content-only change; CI pending)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Skipped		Oct 12, 2026 9:16pm UTC

[cubic-dev-ai]

No issues found across 15 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.

Turn on auto-fix | Re-trigger cubic</sub>

[greptile-apps]

Confidence Score: 5/5

[Low impact] The PR appears safe to merge; no actionable defect was found in the revised content.

Summary

Revises six published changelog articles with clearer behavior, access requirements, and selected release notes.

• Deployment updates explain which workflow edits appear side by side.
• Fork updates show where to compare a source workflow before syncing.
• Intune updates spell out the device and compliance details agents can read.
• Power BI updates explain query, refresh, and access details.
• Nebius updates explain model limits and where to add the API key.
• Agent model updates explain preserved workflows and permission-group defaults.
• Changelog guidance ties fuller stories to product details and release evidence.

_{Reviews (2) · Last reviewed commit: "improvement(changelog): cover release ch..." · Reviewed by Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@waleedlatif1 I have started the AI code review. It will take a few minutes to complete.

[cubic-dev-ai]

No issues found across 15 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Heads up: you’ve reached your flex budget. Increase your flex budget or wait for usage to reset.

Turn on auto-fix | Re-trigger cubic</sub>

[waleedlatif1]

Staging deployment review completed for this revision.

• The reviewed PR CI run 38309625613 and merge-push/deployment run 38310740532 passed, including mobile and desktop checks. A separate historical companion run was cancelled; it is not being reported as a passing check.
• All six hosted articles match the reviewed copy. The selected “Also in” notes, production canonicals, modified dates, original publication dates, and reviewed media are correct. Index, archive, RSS, and sitemap include all six; drafts remain excluded and existing RSS GUIDs are preserved.
• Browser QA passed at 1280px desktop and a real 390px mobile viewport. Images and the existing video poster render correctly, without horizontal overflow. Media and shared-viewer implementation are unchanged from their earlier playback/zoom/focus review.
• Greptile reports 5/5. Cubic reports 5/5 with its stated summary-only budget limitation. There are zero unresolved threads across the complete review-thread result.

Deployed Power BI example. Repository suites ran in CI, as requested. This verifies staging delivery; production publication and the copy revision remain subject to the normal production release and monitor.