chore(cli): require ai-context-core ^1.4.0

[TimCrooker]

Follow-up to #15.

ai-context-cli@1.3.0 depends on core ^1.3.0. That range admits 1.4.0, so a fresh install already picks up the guard that rejects non-root module targets. An existing lockfile does not — it stays pinned to core 1.3.0, keeps the silent-drop behavior, and gives no signal that it is stale.

There was no ordinary upgrade path out of that: pnpm update refuses to move a transitive-only dependency (confirmed against a real consumer — pnpm update @timothycrooker/ai-context-core@^1.4.0 --depth Infinity reports "Already up to date" and churns unrelated packages instead). The only lever left was a hand-written override in each consuming repo.

Bumping the CLI gives consumers the normal path: upgrade the package you actually depend on, and its subtree re-resolves to the fixed core. Tightening the range rather than leaving it at ^1.3.0 also makes the requirement explicit instead of relying on a fresh-lockfile accident.

Templates raised to ^1.1.3 for the same reason — that release carries the corrected meta-skill docs, which previously documented module targets behavior that was never implemented and is what led a consumer into this in the first place.

🤖 Generated with Claude Code

Note

Bump ai-context-cli dependency on ai-context-core to ^1.4.0

Updates the minimum required version of @timothycrooker/ai-context-core from ^1.3.0 to ^1.4.0 and @timothycrooker/ai-context-templates from ^1.1.2 to ^1.1.3 in packages/cli/package.json. This pulls in the core release that rejects non-root module targets with an error instead of silently dropping them.

^{Macroscope summarized 16f149d.}

[macroscopeapp]

Approvability

Verdict: Approved

This PR only bumps dependency version constraints in package.json (^1.3.0 → ^1.4.0, ^1.1.2 → ^1.1.3) and adds a changeset documenting the change. No runtime code is modified - purely a maintenance update to ensure consumers get fixed dependency versions.

^{You can customize Macroscope's approvability policy. Learn more.}