chore(release): v1.0.0-rc.6

[agentcore-devx-automation]

Merging publishes @aws/agentcore@1.0.0-rc.6 to npm and creates the v1.0.0-rc.6 GitHub release with generated notes.

[notgitika]

Looking into failing CI

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.58%. Comparing base (fdf9cf2) to head (57dcce2).
⚠️ Report is 1 commits behind head on refactor.

Additional details and impacted files

@@            Coverage Diff            @@
##           refactor    #2611   +/-   ##
=========================================
  Coverage     96.58%   96.58%           
=========================================
  Files           700      700           
  Lines         57638    57638           
=========================================
  Hits          55672    55672           
  Misses         1966     1966           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[notgitika]

The verify failure on all three OSes is one test: FsProjectManager.create > scaffolds the expected file tree into a fresh directory (src/core/project/manager.test.ts:165).

expect(cdkPackage.dependencies["@aws/agentcore-cdk"]).toBe(MINIMUM_COMPATIBLE_CDK_VERSION);
Expected: "1.0.0-rc.3"
Received: "1.0.0-rc.4"

The scaffold asset (src/assets/cdk/package.json) pins @aws/agentcore-cdk at 1.0.0-rc.4, but MINIMUM_COMPATIBLE_CDK_VERSION in src/core/project/backends/cdk/compatibility.ts is still 1.0.0-rc.3 — the two drifted during the release bump. Fixing by bumping the constant to 1.0.0-rc.4 to match the pin (MIN_MIGRATED_FROM_CDK_VERSION is already rc.4).

Unblocks rc.6. Filing a follow-up to make this a single source of truth so the floor and scaffold pin can't drift again.