# Computer History v1.1.0 — release notes

Computer History v1.1.0 is the stable release of the v1.1 feature set.
Install only on a compatible DSH Host, and back up an existing SQLite history
before upgrading. The version does not guarantee compatibility with every
third-party plugin or untested DSH alpha.

Computer History v1.1.0 extends the Continue-first v1.0 series with
**evidence-backed Work Memory, bounded history retrieval, contextual
continuation, and advisory workflow suggestions**. It does not promise
access to files or data that the collectors never observed.

## What is new

- **Work Memory (M1):** Read-only project reconstruction and retained
  provenance, using trusted Work Thread identities.
- **User-confirmed long-term notes (M2):** Explicitly saved/edited/deleted
  local notes with a separate backup restore flow. Retention and Forget
  boundaries remain distinct; AI note access requires its own scoped grant.
- **Ask Your History (M3):** Natural language-oriented, source-linked history
  exploration that never substitutes speculation for missing observations.
- **AI-first evidence lookup:** The optional,
  metadata-only DSH `computer_history_query` tool filters bounded
  retained Episodes by workspace, app, time, resource type and observed
  activity. `resource_text` searches literal resource names/URIs and,
  with `event_kind=save`, matches the **same saved resource**, not files
  merely viewed alongside a different saved file in one Episode. Build/test
  results remain Episode-level events, **not** proof that a particular file
  was built or tested.
- **Reviewed AI-to-Continue:** Asking DSH AI opens an
  **editable, unsent composer draft**. The user must inspect a cited
  Episode ID and separately confirm Continue. Invalidated, expired or
  mismatched sources cannot be used as verified continuation evidence.
  Continue does not automatically reopen desktop applications or files.
- **Work Thread Intelligence (M4):** Conservative cross-app evidence
  suggestions. Exact canonical file sharing remains advisory, and temporal
  neighbours stay **unattributed**, never silently merged into Continue.
- **Contextual Continue (M5):** Optional same-session M1/M4 history depth,
  bound to an existing Continue session. No change to Continue selection,
  Work State target order, or first-turn injection.
- **Suggested Skills (M6):** Detect recurrent retained activity with at least
  three distinct Episodes across two days. These are **candidate patterns**,
  not safe executable Skills or generated commands.
- **Suggested Automations (M7):** Identify narrow test/build date rhythms
  and offer copyable, user-reviewed reminder **drafts**. No job is created,
  scheduled or run; frequency, time, location and permissions remain the
  user's decisions.

## Security and migration

- Host normalization no longer persists free-form browser page titles
  that can echo URL query secrets. Browser URL credentials, query strings
  and fragments are stripped before storage.
- **Migration 0015** removes legacy browser titles and normalizes retained
  URL identities, safely merging duplicates while preserving citations.
- **Migration 0016:** Episode-retained save/build/test
  facts are derived from actual linked observations. Already-expired raw
  events **cannot** be reconstructed; no retained match is not proof
  that work never happened. Migration 0016 is **forward-only**. Upgrade
  requires an approved, consistent backup and a verified disposable
  restore; rollback means **restore**, not in-place schema downgrade.
  When WAL/SHM files are active, never copy `history.sqlite` alone.
- Importing older JSON backups also re-sanitizes browser metadata and
  recomputes newly imported browser Episode summaries. Previous exports
  produced by old versions may still contain sensitive data and must be
  treated as such.
- No new default capture scope, automatic remote AI disclosure, model call,
  background job or permanent cross-project identity inference.

## Evidence collected before this draft

- PRs M1–M7 and the browser-title/privacy hotfix were merged to main,
  each passing their required CI.
- macOS DSH `0.2.1-alpha.2` + Chrome *installed package* journey passed
  **59 product checks**, including first run, trusted Editor/Browser,
  Episodes, Continue, disable/re-enable/uninstall, browser title privacy,
  M1 project view and M6/M7 truthful empty states.
- Windows real Notepad→UIA→Host/SQLite and three-platform package CI
  passed on the privacy hotfix.
- An authorized, local, consistent SQLite online backup and independent
  restored-copy migration rehearsal passed from actual schema v13 to v16
  without changing the original database. This does not automatically upgrade
  any existing installation.

## Important limitations / user actions

- The AI-first query does **not** read file contents, enlarge collector
  permissions or automatically contact a model. If a remote model is
  separately enabled, a reviewed prompt/Continue context may be sent to it;
  this is not a guarantee of offline-only operation.
- Fixture-model Find → Answer → Continue integration and the CI-packaged
  client tests are **not** live-model synthetic end-to-end acceptance or
  native Electron History/Settings click-flow acceptance. These remain
  documented post-release acceptance work, not claims of completed testing.
- **Host compatibility:** tested with DSH `0.2.0-rc.2` and `0.2.1-alpha.2`,
  not arbitrary DSH builds. A separately installed `dsh` command on PATH may
  have a different version from the running Electron Desktop's embedded Host;
  check the actual Host before installing. DSH `0.1.x` is unsupported.
- The existing SQLite history cannot be backed up reliably by copying
  `history.sqlite` while a WAL/SHM is present. Follow
  [the read-only upgrade preflight and restore plan](../upgrade-v1.1-preflight.md)
  before authorizing any live migration.
- Real populated multi-project suggestion quality and safe user-level
  backup/rollback are distinct acceptance gates; synthetic and one-Episode
  product checks do not prove all user histories will yield useful Skills.
- No installer or automated scheduler should be enabled merely because
  an M6/M7 candidate is displayed.

## Release verification and follow-up

- **Source and CI:** 933 tests passed (2 skipped) and all eight GitHub Actions
  workflows passed on the integrated candidate, including Dependency Review.
- **Package:** one SHA-verified tarball with Windows, macOS and Linux native
  collectors passed packaged clean-install and installed product tests on
  all three CI operating systems.
- **Migration:** a local, access-restricted SQLite online backup passed
  integrity and foreign-key checks; v13→v16, checksum-failure and restore
  rehearsals passed on disposable copies. Users must make and validate
  *their own* consistent backups prior to upgrade.
- **Known gaps:** full native Electron keyboard/VoiceOver interaction, a
  live-provider synthetic AI answer and arbitrary third-party plugin
  combinations have not been exhaustively validated. These are tracked as
  follow-up QA, not advertised as verified. Opt-in remote model calls and
  collector permissions remain explicit user decisions.
- **Deployment:** publication of this package does not itself migrate any
  existing user profile, enable capture or install the plugin into DSH.

The `v1.0.0` and `v1.0.1` GitHub/npm artifacts are immutable: never
retag or republish them with v1.1 content.