fix(cdk): align yarn.lock with upstream main + bump table count for OAuth registry

Two CI failures came together because they share a root cause: this
branch's yarn.lock had drifted from upstream main during interim
re-resolves, leaving an inconsistent dep tree that broke ts-jest's
module resolution for @aws-cdk/mixins-preview/aws-bedrockagentcore.
Restoring upstream main's yarn.lock fixes the resolution; the
agent.test.ts table-count assertion then needs to bump from 12 to
13 to account for the LinearWorkspaceRegistryTable added in
Phase 2.0b Wave A4.

Verified locally: agent.test.ts (44/44) and github-tags.test.ts
(5/5) both pass after the changes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: bgagent

cdk/test/stacks/agent.test.ts

@@ -36,12 +36,13 @@ describe('AgentStack', () => {
     expect(template).toBeDefined();
   });
 
-  test('creates exactly 12 DynamoDB tables', () => {
+  test('creates exactly 13 DynamoDB tables', () => {
     // task, task-events, repo, user-concurrency, webhook, task-nudges,
     // task-approvals (Cedar HITL V2),
     // slack-installation, slack-user-mapping,
-    // linear-project-mapping, linear-user-mapping, linear-webhook-dedup
-    template.resourceCountIs('AWS::DynamoDB::Table', 12);
+    // linear-project-mapping, linear-user-mapping, linear-webhook-dedup,
+    // linear-workspace-registry (added in Phase 2.0b for OAuth bookkeeping)
+    template.resourceCountIs('AWS::DynamoDB::Table', 13);
   });
 
   test('creates TaskApprovalsTable with user_id-status-index GSI', () => {