refactor(framework)!: rename package to @gemstack/the-framework and CLI to the-framework (#1071)

[suleimansh]

Closes #1071.

Renames the published package @gemstack/framework -> @gemstack/the-framework and the CLI command framework -> the-framework, for consistency with the product name The Framework (the direction #1071 argues for).

What changed (125 files)

• packages/framework/package.json: name and the bin key (framework -> the-framework).
• Every import site: framework-dashboard (components/lib/server), examples/, and the framework's own runtime refs: update-check.ts PACKAGE_NAME (the npm name it polls for updates), and the node_modules/@gemstack/the-framework/prompts/... paths in system-prompt.ts + tickets.ts.
• CLI command references in the active READMEs (root + packages/framework + demo), re-aligned help columns.
• Changesets: the 36 pending changeset frontmatter keys were flipped to the new name (otherwise changeset version errors on a missing package), plus one new major changeset for the rename itself.
• Regenerated pnpm-lock.yaml.

Deliberately untouched

• CHANGELOG.md history (accurate record of past @gemstack/framework releases).
• The English word "framework" and the separate @gemstack/framework-dashboard package (boundary-safe replace).
• The directory packages/framework/ (internal, not user-facing; repository.directory unchanged).

Verification (local, this branch)

• pnpm build 12/12, pnpm typecheck 22/22
• framework tests 1172 pass / 0 fail / 1 skip
• dashboard tests 383 pass / 0 fail
• check-prompt-drift in sync

Notes for the reviewer / release coordination

• npm rename is not a rename: @gemstack/the-framework is a new package; @gemstack/framework stays published and needs a manual npm deprecate pointing at the new name (post-merge step).
• Release PR chore: version packages #1012: merging this makes the changeset bot regenerate chore: version packages #1012 to publish under the new name. Recommend not merging chore: version packages #1012 separately first.
• Bump level: I defaulted the rename changeset to major (2.0.0) as a clear breaking signal. Happy to change to minor/patch if preferred.
• The repo rename (Rename repo to the-framework #655) and its ~65 in-repo URL references are a separate follow-up PR, coordinated with the GitHub Settings rename.