v0.7.0

• Opt-in per project (breaking default change). A globally-installed plugin no longer
  activates in every workspace. Presence of .engraim/ is the sole opt-in signal:
  • The SessionStart hook is fully silent in a project that hasn't opted in — it creates
    nothing and injects nothing (previously it auto-bootstrapped .engraim/ on first session).
  • The MCP server refuses to auto-create a workspace: every tool except the new opt-in
    tool no-ops with a pointer to /engraim:init until .engraim/ exists.
  • New enable tool + cli enable subcommand are the only paths that adopt a project;
    /engraim:init, /engraim:onboard, and /engraim:backfill call it first.
  • Existing opted-in workspaces are unaffected (they already have .engraim/).

v0.6.0

• Proactive upkeep nudges — so the self-improvement loop never depends on the user
  remembering the commands. Two new hooks plus a richer SessionStart:
  • UserPromptSubmit (user_prompt.sh → cli user-prompt): deterministic phrase
    detection surfaces a calibrate nudge on durable, project-wide feedback ("from now on",
    "always remember", "in this project", "prefer X over Y", …), and a 6h-throttled reminder
    of pending curate/retro/skill upkeep so long sessions don't drift.
  • PostToolUse (tool_followup.sh → cli post-tool, matched on calibrate / draft_skill
    / ingest_session / mark_onboarded): chains the natural next step — calibrate → curate +
    promote-override, draft-skill → promote-skill, onboard → backfill, curate → retro.
  • SessionStart now also surfaces a /engraim:retro pass once its inputs (expiring
    overrides, promotion candidates, ≥6 staged sessions) accumulate.
  • All nudges are model-gated (the hook detects; the model decides whether to act) and
    covered by the self-test.
• Release tooling — scripts/bump-version.mjs <version|major|minor|patch> keeps the two
  release-version sources (marketplace.json, plugin.json) in lockstep and flips the
  ## Unreleased CHANGELOG heading. The self-test now guards that the two versions agree.
  A Release workflow tags + publishes a GitHub Release on merge to main when the version
  changed (idempotent — ordinary merges no-op). The workspace schema version is untouched.