# Prompt Journal Restoration

audience: AI coding agents first.

status: ACTIVE
worker: main session landing deploy-path fix
task IDs: #121, #235
source request: Durable prompt history must survive compaction and be queryable; restore the missing installed entrypoint.

## Outcome

Every owner prompt is durably captured, queryable, and recoverable through the installed `prompt-journal` entrypoint.

## Preserved evidence

- #121 registry says completed.
- `/home/user/.local/bin/prompt-journal` was measured absent.
- Full session transcript remains at `/home/user/.claude/projects/-home-user/f5f6f15f-b816-485f-b134-63385afdc36e.jsonl.live.jsonl`.
- Do not rebuild capture semantics before locating prior source/commit.

## Acceptance criteria

- Installed entrypoint exists and resolves to landed/deployed source.
- New owner prompt appears exactly once.
- Query returns it after session restart.
- Synthetic notifications are distinguishable/excluded from owner-message recovery.

## Execution steps

1. Locate prior #121 source/commit and deploy mapping.
2. Verify source behavior with focused tests remotely.
3. Install live entrypoint.
4. Run capture/query probe.
5. Land/deploy and update receipt.

## Current receipt

Prior source recovered at `f4b7c416`/`ddc1390b`; remote focused suite passed 42/42. Live `~/.local/bin/prompt-journal` now resolves to the deploy clone. Live backfill appended 1,243 records with zero malformed lines and queried the latest owner prompt exactly. Standard deploy omitted `manifest/bin.json`; `packaging/deploy-local.sh` now applies that manifest. First remote deploy-suite run exposed incomplete fixture coverage caused by the new command (10 pass/11 fail): fixture omitted `bin.json` and dry-run contract omitted the new step. Both test contracts were corrected; authoritative remote rerun `b3jh4y5aq` passed 21/21 cleanly. Fix and plan chain landed/pushed through `9b7681c9`. Valid runtime fleet state was then preserved and landed as `c19f4841`: Debian2 is `unreachable` and excluded from build/e2e order. Deploy clone is now clean, detached at `c19f4841`, and matches `origin/main`; standard deployment `b81apw5jr` is running. A peer's `draining` report described stale pre-repair state, not current clone state.

## Next executable action

Consume standard deployment `b81apw5jr`; then run installed-path and query proof and mark DONE only if both succeed.
