fix: lazy-load scheduler AWS SDK in core and repair frigg init scaffolding

[seanspeaks]

Summary

Two independent packaging bugs on next, both of which make a clean install unusable before any real work starts.

Fix 1 — @friggframework/core should not require @aws-sdk/client-scheduler unless EventBridge is actually used

infrastructure/scheduler/eventbridge-scheduler-adapter.js did a top-level require('@aws-sdk/client-scheduler'), and scheduler/index.js eagerly requires that adapter (which core loads via application → scheduler-commands). Core never declared the package, so on a clean install merely running require('@friggframework/core') threw MODULE_NOT_FOUND — even on the mock provider or with no AWS at all. This also broke the devtools CLI, which loads core (verified: frigg init --help crashed on the unfixed registry core).

Approach (dep made lazy, not just added):

• @aws-sdk/client-scheduler is now required lazily through a cached loadSchedulerSdk() helper, called from the EventBridge adapter's constructor and methods — never at module load. Requiring the scheduler module (and thus core) no longer pulls aws-sdk; only instantiating the EventBridge adapter does. A missing package yields a clear, actionable error instead of a raw MODULE_NOT_FOUND.
• Declared in optionalDependencies so AWS deployments still install it by default, while non-AWS/local consumers aren't forced to. The factory already only instantiates the EventBridge adapter for the eventbridge provider; the mock path never touches aws-sdk.
• Added a regression test (eventbridge-scheduler-adapter.test.js).

Proof (clean temp install, --omit=optional so client-scheduler is absent):

BEFORE (top-level require): Error: Cannot find module '@aws-sdk/client-scheduler'
AFTER:  require('@friggframework/core') SUCCEEDED without @aws-sdk/client-scheduler

• Mock provider works and is the dev/test/local default; installing @aws-sdk/client-scheduler and instantiating EventBridgeSchedulerAdapter still constructs a real SchedulerClient.
• New regression test: 4 passing.

Fix 2 — frigg init is broken in the 2.0-next devtools

frigg init <name> failed two ways:

(a) Backend template not shipped. The handler copies from frigg-cli/templates/backend, but that directory did not exist in the source tree (confirmed absent from the published 2.0.0-next.107 tarball) → "Backend template not found." Added a working backend template (index.js exporting Definition, infrastructure.js, README.md) and listed frigg-cli/templates/ in package files. The template's app definition validates against the current app-definition schema, and carries the exact markers updateAppDefinition() rewrites when integrations are selected.

(b) The --template default routed every init into the dead legacy branch. The CLI registered --template with a default of 'backend-only', but the handler only runs the backend-first path when !options.template, so the truthy default always fell through to "Legacy template system is no longer supported" and exited 1. Removed the default (--template is now an explicit, unsupported legacy opt-in), made the positional the project name (init [projectName]), registered the flags the handler actually reads (--mode, --no-frontend, --force, --verbose), dropped the unused --directory, and removed the dangling options.legacyFrontend reference.

Proof (built devtools tarball installed into a scratch dir):

• frigg init --help lists the new options.
• Scaffolding my-frigg-app produces index.js / infrastructure.js / package.json / README.md — no "template not found", no "legacy not supported". Generated index.js exports a valid Definition; infrastructure.js resolves createFriggInfrastructure from devtools.
• Explicit --template still shows the legacy message (escape hatch preserved).

Files changed

• packages/core/infrastructure/scheduler/eventbridge-scheduler-adapter.js — lazy SDK load
• packages/core/infrastructure/scheduler/eventbridge-scheduler-adapter.test.js — new regression test
• packages/core/package.json — optionalDependencies: @aws-sdk/client-scheduler
• packages/devtools/frigg-cli/templates/backend/{index.js,infrastructure.js,README.md} — new backend template
• packages/devtools/package.json — ship frigg-cli/templates/
• packages/devtools/frigg-cli/index.js — init command definition
• packages/devtools/frigg-cli/init-command/index.js — default routing + project-name handling

Test plan

• Clean-install core without client-scheduler → require succeeds (threw before)
• Mock scheduler works; EventBridge adapter still functions with SDK present
• Scheduler regression test passes (4/4)
• frigg init <name> scaffolds a backend app from the built devtools tarball

🤖 Generated with Claude Code

---

Generated by Claude Code

[claude]

Claude Code Review

Claude Code Review is paused for this repository. To reconnect it, an admin of this repository's GitHub organization (or the account owner, for personal repositories) who can also manage your Claude organization's Code Review settings needs to re-link GitHub in Code Review settings. This is a one-time step.

_{Tip: disable this comment in your organization's Code Review settings.}

[netlify]

✅ Deploy Preview for friggframework-org canceled.

Name	Link
🔨 Latest commit	f788c5e
🔍 Latest deploy log	https://app.netlify.com/projects/friggframework-org/deploys/6a853bd821c7540008f66669

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud