Skip to content

v0.5.1

Choose a tag to compare

@github-actions github-actions released this 10 Sep 11:16
· 16 commits to main since this release

Changed

  • Distribution is git-only. The release workflow no longer publishes to npm: it checks that the
    tag matches package.json, re-checks the committed dist/, and creates the GitHub release from
    the matching CHANGELOG.md section. pi install git:... is the only documented install path,
    and the npm badge and npm install/uninstall sections were removed from both READMEs.
  • The store file is created 0600 where the OS supports it (ignored on Windows).
  • Errors returned to the model by memory_search/memory_expand no longer contain absolute local
    paths; the full trace stays in the extension log.
  • CI limits the workflow token to contents: read, the release workflow extracts release notes
    with a literal version match instead of a regular expression, and the declared
    billion-context-pi peer range is >=0.1.65 to match the documented tested version.
  • The install docs are written for the public repository: HTTPS first (no credentials required),
    SSH as the alternative, plus an "Update" section and a release badge.
  • Both workflows pin actions/checkout and actions/setup-node to commit SHAs. The repository
    also gained issue forms (bug report with version/Node/pi fields), a pull-request template,
    Dependabot configuration, and a Code of Conduct.

Added

  • README "Scope: single user, single machine" section: no accounts, server, sync, or per-user
    permissions; one store per OS user; SQLite WAL locking is single-host only, so the database file
    must never be shared; ephemeral homes rebuild the index; redaction is best-effort over a
    plaintext, permission-unhardened store; sync sidecars, not the database, across machines.

Fixed

  • memory_expand hardening after an external review of 0.5.0:
    • mode: "full" now requires a non-empty select instead of rendering the whole block,
      which contradicted the documented two-step contract.
    • expandMaxReadBytes is a real read cap again: the session file is opened and read in bounded
      chunks instead of being slurped whole and sliced afterwards.
    • A per-entry trim is reported as truncated again (a later assignment always cleared the
      flag), and the rendered text is guaranteed to stay within maxChars.
    • A missing/renamed session file degrades to missing references instead of throwing, matching
      the documented behavior.
    • custom_message entries (extension-injected context such as ACP compaction notices) are
      expandable again; unknown content-item types render an explicit [unsupported ...]
      placeholder instead of being dropped from the entry.
    • Re-ingesting a sidecar clears stored pointers the sidecar no longer lists, so expansion can no
      longer return messages that are no longer part of the block.
    • The 0.5.0 pointer migration now clears a freshly seeded watermark row, so an orphaned source
      row still gets its pointers backfilled.
    • ~ in dbPath/sourcesPath/logPath expands to the home directory instead of creating a
      literal ~ directory.
    • The ambiguous-block message reports the real number of matches instead of the page size.
    • Manifests no longer print an absolute session path, and generated acp_summary_* references
      are labelled synthetic rather than counted as recoverable text.
  • Scan and store lifecycle hardening after a follow-up review:
    • A background scan can no longer reopen the closed store after session_shutdown: the scan
      aborts per file when the session generation moved on, and getDb() refuses to open a latched
      store instead of recreating it.
    • One failing allow-list source (unreadable root, corrupt opencode DB, adapter bug) no longer
      aborts every remaining source; failures are counted and logged per source.
    • An allow-list entry with an unknown adapter is rejected and logged when the list is read,
      instead of falling through to the permissive scan-time path.
    • /memory prune writes its tombstones and deletes in one transaction, so a crash cannot leave
      the two halves inconsistent, and a failing VACUUM is logged instead of failing the prune.
    • An ingest that finishes reading a file after session_shutdown returns store closed instead
      of touching a null handle and then failing again in ROLLBACK.
    • A scan whose allow-list root holds more than 20,000 entries stops at the cap and logs it,
      instead of walking an accidentally over-broad tree to the end.
    • Log lines no longer contain absolute session or working-directory paths unless debug is on
      (the store path is logged as a file name) — logs are what users paste into public issues.
    • SECURITY.md no longer points "above" at a section that sits below it.