# changelog

what changed for someone using `/lore`. versions are the npm package
[@waow.tech/lore](https://www.npmjs.com/package/@waow.tech/lore); `pi update`
picks up the latest.

## 0.2.0 — 2026-10-01

- requires the October 1 Spaces alpha contract. run `pi update` and reload
  the extension; existing project keys and stored entries stay the same.
- credential issuance and reads use HTTP signatures with DID-bound keys
  and audiences. credentials refresh before expiry and once after a 401.
- sharing grants explicit read and write access; creation sets separate
  read and write policies. the website uses the same contract.
- all writer and record pages are read, including a final short page with
  a cursor. website credentials are isolated by signed-in account.
- writes rely on the repo host's notification delivery; the client-side
  announcement workaround and member-list fallback have been removed.

## 0.1.2 — 2026-09-05

fixes from the first reports in the field, reproduced against two host
implementations before shipping.

- **"the agent spins forever after remember."** the tool was waiting for
  the "save to …?" dialog while the status line said "working", so a dialog
  you didn't notice looked like a hang. lore's own line now says it is
  waiting for your answer, the dialog counts down two minutes, and if nobody
  answers the agent is told nothing was saved and says so.
- **your lines were invisible to the space owner when your PDS is not the
  space's host.** a write on your PDS is announced to the host, and one host
  (zds) rejected every announcement from the reference PDS over a base64
  padding difference. lore now announces its own writes in the form every
  host accepts, and an owner reads each member's repo directly whether or
  not the host lists it. the host was fixed too.
- **`/lore share` failed on accounts hosted by the reference PDS** (the
  spaces alpha host among them), because that host answers with an empty
  body and lore expected `{}`. an empty answer is accepted now.
- `/lore` re-reads the space; what others wrote since the session began
  arrives as a message on the next turn.
- pasted handles work: `https://zat.dev`, `@zat.dev`, and a trailing dot are
  cleaned before resolving.
- a folder with no git remote no longer gets a space keyed on its path;
  name one with `/lore use <key>`. the picker for `use` offers the keys you
  already own.

## 0.1.1 — 2026-09-03

- the space is rendered into the prompt once per session and never
  re-rendered, so saving a breadcrumb no longer breaks the model's prompt
  cache. the session's own saves are already in the transcript.

## 0.1.0 — 2026-09-03

- first publish to npm. `pi install npm:@waow.tech/lore`.