@timurproko/a1 0.1.8-dev.290 → 0.1.8-dev.322

package/docs/architecture/project-structure.md

@@ -13,6 +13,7 @@ src/
   features/
     launch/                        launch profiles, profile paths, and runtime selection
     owned-ui/                      owned screens, settings application, diagnostics, and runtime lifecycle
+    prompt-history/                profile-isolated prompt retention and bounded SQLite worker lifecycle
     workspace/                     multi-agent presentation, reducer state, routing, and persistence orchestration
   contracts/
     agent-engine/                  dependency-free agent engine, session, package, and capability ports

package/docs/architecture/resource-and-data-policy.md

@@ -31,7 +31,8 @@ Every asynchronous consumer must implement a finite queue or window. Backpressur
 | Class | Examples | Storage policy |
 |---|---|---|
 | Workspace metadata | IDs, names, lifecycle, capability versions, topology revisions, recovery references | May persist in the control store |
-| Structured payloads | Messages, tool calls, snapshots, attachments | Bound and process; persist only under a future typed retention policy |
+| Structured payloads | Messages, tool calls, snapshots, attachments | Bound and process; arbitrary payload persistence remains unsupported |
+| User-authored prompt recall | Canonical interactive input and bounded provenance | May persist only through the profile-isolated prompt-history policy below, never in the control store |
 | Terminal content | PTY bytes, scrollback, selection, rendered cells | Never persist in A1's control store or diagnostics |
 | Host topology metadata | Window/tab/pane/session IDs, layout shape, dimensions, revision | May persist; not terminal content |
 | Native proof evidence | Artifact hashes, source revisions, workloads, latency/resource measurements, paint diagnostics | May persist in versioned evidence files without terminal content |
@@ -42,6 +43,31 @@ Every asynchronous consumer must implement a finite queue or window. Backpressur
 
 Sanitization must classify before logging or storing. Unknown or untyped values are potentially sensitive by default and must not be persisted. Terminal bytes must never be written to logs as a debugging shortcut.
 
+## Typed prompt-history retention
+
+The `prompt-history` feature owns only reusable interactive user input, not
+structured-message archives. It stores one independent profile database under
+`<effective-home>/.a1/data/history`, or `<A1_DATA_DIR>/history` when explicitly
+overridden, never agent resources or cache/release directories. The default home
+follows launch-profile resolution, including `A1_PROFILE_HOME`; other product
+data paths are unchanged. Text is unencrypted and potentially sensitive. Retain up to 100 unique entries (configured
+10-100), at most 1 MiB per entry and 8 MiB total canonical text. Background queues
+are limited to 32 writes/8 MiB per instance; reads are coalesced, lock retries are
+bounded to one second off-thread, and graceful shutdown drains for at most two
+seconds. SQLite page/journal limits and a 64 MiB maintenance threshold bound
+physical growth separately from text retention.
+
+Only typed canonical text, submission identity, recency/timestamp, input kind,
+and bounded cwd/session provenance are allowed. No image bytes, transformed
+agent prompts, environment/credential copies, tool results, terminal streams, or
+private input in diagnostics are permitted. Disabling persistence is next-start
+and does not erase data or stop other live instances. Upgrades, ordinary npm
+uninstall/reinstall, and cache/release cleanup must not touch history. The new
+default starts fresh without probing, importing, or deleting the old platform
+store. Any old-store removal is a separate manual operation after its users have
+stopped, not startup or cleanup behavior. See [prompt history](../features/prompt-history.md) for
+retention, failure semantics, profile identity, and stopped-instance removal.
+
 ## Required architectural outcomes
 
 - Structured/RPC semantics must not be inferred from ANSI text, terminal timing, or visual content.

package/docs/architecture/toolchain.md

@@ -82,7 +82,7 @@ These paths are A1 control and release state, not Pi profile roots. All are over
 | Purpose | Override | Windows default | Unix default |
 |---|---|---|---|
 | Config | `A1_CONFIG_DIR` | `%APPDATA%\\a1` | `$XDG_CONFIG_HOME/a1` or `~/.config/a1` |
-| Durable data | `A1_DATA_DIR` | `%LOCALAPPDATA%\\a1` | `$XDG_DATA_HOME/a1` or `~/.local/share/a1` |
+| Control/release data | `A1_DATA_DIR` | `%LOCALAPPDATA%\\a1` | `$XDG_DATA_HOME/a1` or `~/.local/share/a1` |
 | Runtime | `A1_RUNTIME_DIR` | `%LOCALAPPDATA%\\a1\\runtime` | `$XDG_RUNTIME_DIR/a1` or `<data>/runtime` |
 | Database | `A1_DATABASE_PATH` | `<data>/control.sqlite3` | `<data>/control.sqlite3` |
 | Endpoint | `A1_ENDPOINT` | runtime-scoped `a1-*` named pipe | `<runtime>/supervisor.sock` |
@@ -96,3 +96,17 @@ Do **not** remove `~/.a1/agent`; it is A1's current Pi profile root. `~/.pi/agen
 The obsolete npm package `@timurproko/addone` is deprecated with the registry message `This package is obsolete. Use @timurproko/a1 instead.` It is not a current identity, compatibility channel, or rollback source. Whole-package unpublication was rejected by npm policy; any later removal is owner-controlled registry administration and does not change the A1 runtime contract.
 
 The launch-profile feature separately owns A1's `~/.a1/agent` root and preserves ordinary Pi resolution through `~/.pi/agent`.
+
+## Internal naming validation
+
+The required PR naming job inspects complete new and changed source files. `npm run check:names` performs the full tracked audit, also required by nightly full-release validation. See [internal naming and clean cutover](internal-naming.md) for public/private environment ownership, required checks, and protected user data.
+
+### Prompt history
+
+Prompt history has a separate default: `<effective-home>/.a1/data/history/<profile-id>.sqlite3`
+on Windows, Linux, and macOS. The effective home follows launch-profile resolution
+(`A1_PROFILE_HOME` or the OS home), not `XDG_DATA_HOME`. An explicit `A1_DATA_DIR`
+continues to select `<A1_DATA_DIR>/history` as well as the control/release data root.
+The home-based history default does not relocate the paths above or the compile
+cache at `<data>/cache/compile`. See [prompt history](../features/prompt-history.md)
+for the deliberate fresh start without migration, privacy, and manual removal.

package/docs/features/prompt-history.md

@@ -0,0 +1,149 @@
+# Persistent prompt history
+
+Bare A1 recalls recent prompts across sessions and projects within the same A1
+profile. It is input recall, not conversation recovery or agent memory. The Pi
+comparison (`a1 pi`) retains its ordinary current-session history.
+
+## Recall
+
+Use Up/Down at the editor's normal history boundaries. Up enters older prompts
+with the caret at the end; Down enters newer prompts at the beginning. Moving
+past the newest restores your draft, including its cursor and live pasted text.
+Multiline cursor movement and autocomplete keep their existing priority.
+
+The existing editor border shows `History 100/100` for the newest of 100 entries
+and `History 1/100` for the oldest. The label uses the status bar's neutral grey
+(`dim` theme role), independently of the thinking/bash colors on the input bars. Repeated prompts move forward instead of
+creating duplicates. Other instances refresh in the background; the selected
+history and its count stay fixed until you leave that browse cycle. An
+extension-provided custom editor keeps its own behavior; the default editor is
+resynchronized when restored.
+
+Ordinary prompts, steering, follow-ups, queued inputs, nonempty bash commands,
+and user-entered skill/template/extension prompt routes are eligible. Opening
+settings or session/workflow screens does not add history. Loading a transcript,
+retrying a dispatch internally, draining a queue, or displaying a suggestion does
+not create another entry. An explicit user submission is retained even if the
+provider later rejects it or the turn is interrupted.
+
+Text pastes, URL targets, and file paths remain reusable after restart. History
+keeps the user invocation before template/extension expansion, not the expanded
+request. Image-bearing prompts retain only their text; images are not reattached.
+Image-only prompts do not create saved entries. No v2, Pi, or Claude history is
+imported automatically.
+
+## Storage and privacy
+
+| Platform | Default durable location |
+|---|---|
+| Windows | `%USERPROFILE%/.a1/data/history/<profile-id>.sqlite3` |
+| Linux and macOS | `~/.a1/data/history/<profile-id>.sqlite3` |
+| Explicit override | `<A1_DATA_DIR>/history/<profile-id>.sqlite3` |
+
+The default uses A1's effective profile home: `A1_PROFILE_HOME` when set, otherwise
+the operating-system home. A custom agent-profile directory changes the history
+identity, not this default root. `A1_DATA_DIR` takes precedence for storage;
+`XDG_DATA_HOME` does not redirect default history. Control metadata, settings,
+agent resources, releases, logs, runtime files, and caches keep their existing
+locations.
+
+**The home-based default starts fresh.** Previous versions used
+`%LOCALAPPDATA%/a1/history` on Windows, or `$XDG_DATA_HOME/a1/history` /
+`~/.local/share/a1/history` on Unix. A1 does not probe, import, merge, delete, or
+fall back to those stores. Explicit `A1_DATA_DIR` selections still work normally.
+Old and new releases using different roots do not synchronize history.
+
+The profile filename is `a1-` followed by a SHA-256 digest of a versioned tuple
+containing the launch kind and normalized effective agent-profile path. It is
+independent of project, session, checkout, and release. Windows ordinary case and
+separator variants normalize together. Different profile roots use different
+files. Moving a profile, unresolved symlink aliases, or selecting a different
+data root can select a different history; A1 never silently merges or imports it.
+
+The database is separate from `control.sqlite3`, agent resources, and disposable
+caches. Upgrades, ordinary npm uninstall/reinstall, release rollback, cache cleanup,
+and conversation deletion do not clear it. Reusing saved history requires the
+same profile and history root; explicitly deleting user data still removes it.
+SQLite may keep `-wal` and `-shm` sidecars beside the database.
+
+**History is unencrypted potentially sensitive user text.** Owner permissions
+are restricted where supported; Windows uses inherited ACLs at the selected
+history directory. Review parent-directory permissions if you customize your home
+or override root. These protections do not make it safe to submit secrets.
+Credential files, image data, arbitrary environment values, assistant/tool output, and terminal
+streams are not copied into this store. Prompt content and private provenance
+must not appear in history diagnostics or test evidence.
+
+## Settings and limits
+
+The History section in `/settings` provides:
+
+- **Persistent history:** on by default; applies on the next start. Off disables
+  storage and cross-session recall for subsequent launches, not current-session
+  recovery. Existing enabled instances keep running until closed.
+- **History limit:** 10-100 in increments of 10, default 100; applies when a new
+  enabled instance starts. All writers then use that profile store's updated
+  retention limit. Raising the limit cannot restore pruned entries.
+
+The settings use A1's existing settings document, not Pi's settings or a separate
+history configuration file. Disabling persistence does not delete saved data;
+re-enabling makes compatible retained entries available again.
+
+Additional bounds protect memory and disk:
+
+- At most 1 MiB UTF-8 per persisted prompt, never silently truncated.
+- At most 8 MiB retained canonical text, evicting oldest entries even below the
+  configured count.
+- At most 32 queued/in-flight writes and 8 MiB queued text per instance.
+- Provenance: up to 8 KiB cwd and 256 bytes session identity; oversized optional
+  provenance is omitted.
+- Short off-thread transactions, a one-second lock retry window, and coalesced
+  refresh with at most one read in flight.
+- SQLite page/journal limits and a 64 MiB database/sidecar maintenance threshold;
+  text limits exclude transient SQLite overhead.
+
+Persistence failure leaves prompt execution and local recall usable. A corrupt,
+wrong-profile, or newer-schema database is preserved, not silently recreated.
+A committed entry survives restart. A hard kill before asynchronous commit can
+lose the newest queued entries. Graceful exit attempts to drain writes within
+two seconds and reports an incomplete flush without preventing exit.
+
+## Remove saved history
+
+First close **every instance using the selected profile**. Then remove only that
+profile's `.sqlite3` file and its matching `-wal` and `-shm` sidecars, if present.
+Do not delete an open database, the whole `.a1` directory, or the whole
+application-data root. Disabling the setting alone is not an erase operation.
+There is no interactive clear/export command in this release.
+
+Removing a former default store is likewise a one-time manual cleanup, not an
+application feature. Wait until you have switched to the new version and closed
+all instances using the old store; an older running version can otherwise keep
+using or recreate it. Remove only the identified old profile database and matching
+sidecars, not other profiles or either application's caches.
+
+## Manual acceptance
+
+Build the checkout, then launch it through `./scripts/dev`. Use an isolated
+`A1_DATA_DIR` for disposable history checks; keep that same directory on each
+restart and in both concurrent terminals. The development launcher always sets
+an isolated `A1_DATA_DIR`; to try the home-based location in that launcher,
+explicitly select `A1_DATA_DIR=<effective-home>/.a1/data` and keep
+`A1_DATABASE_PATH` in a separate disposable directory so control metadata is not
+placed beside history. For a history-only review, `NODE_DISABLE_COMPILE_CACHE=1`
+also avoids creating compile-cache files under that explicitly overridden root.
+The focused path/composition tests cover normal no-override selection. Test:
+
+1. Submit two text prompts and one repeated prompt; start `/new`, then restart.
+   The latest unique prompts remain recallable.
+2. Browse multiline input with a draft present. Check v2 caret placement,
+   newest/oldest numbering, and draft restoration.
+3. Submit from a second instance while the first browses. The first selection
+   stays fixed; the update appears on a later safe browse cycle.
+4. Recall pasted text after restart; image tokens must not promise reattachment.
+5. Save both History settings, restart, and verify effective values and opt-out.
+6. Use a second isolated effective profile and verify no sharing. Run
+   `./scripts/dev pi` and verify its ordinary history/editor remain unchanged.
+
+Source ownership and differential editor evidence are described in
+[history-editor-provenance.md](../architecture/history-editor-provenance.md).

package/package.json

@@ -1,8 +1,9 @@
 {
   "name": "@timurproko/a1",
-  "version": "0.1.8-dev.290",
+  "version": "0.1.8-dev.322",
   "description": "Standalone terminal workspace for supervised native and managed agents",
   "type": "module",
+  "privateLaunchContract": "neutral-launch-v1",
   "packageManager": "npm@11.13.0",
   "bin": {
     "a1": "bin/cli.js"
@@ -26,7 +27,9 @@
     "build": "npm run clean && tsc -p tsconfig.build.json && node scripts/development/build-process-guardian.mjs && node scripts/release/generate-runtime-payload-inventory.mjs",
     "build:process-guardian": "node scripts/development/build-process-guardian.mjs",
     "typecheck": "tsgo -p tsconfig.json --noEmit",
-    "check:architecture": "node scripts/governance/check-architecture.mjs && node scripts/governance/product-identifier-policy.mjs --check && node scripts/governance/check-product-identity-boundaries.mjs && node scripts/governance/check-package-identity.mjs && node scripts/governance/check-pinned-pi-source-ledger.mjs && node scripts/governance/check-terminal-host-provenance.mjs",
+    "check:architecture": "node scripts/governance/check-architecture.mjs && node scripts/governance/check-product-identity-boundaries.mjs && node scripts/governance/check-package-identity.mjs && node scripts/governance/check-pinned-pi-source-ledger.mjs && node scripts/governance/check-terminal-host-provenance.mjs",
+    "check:names": "node scripts/governance/product-identifier-policy.mjs --check",
+    "check:names:changed": "node scripts/governance/product-identifier-policy.mjs --check --selection .artifacts/validation/impact.json",
     "check:code-documentation": "node scripts/governance/check-code-documentation.mjs --mode full",
     "check:code-documentation:changed": "node scripts/release/run-changed-documentation.mjs",
     "select:validation-impact": "node scripts/release/select-validation-impact.mjs",
@@ -70,6 +73,7 @@
     "undici": "8.9.0"
   },
   "devDependencies": {
+    "@lezer/python": "1.1.19",
     "@types/cross-spawn": "6.0.6",
     "@types/node": "24.2.1",
     "@types/semver": "7.8.0",
@@ -78,7 +82,8 @@
     "node-pty": "1.1.0",
     "tsx": "4.20.3",
     "typescript": "5.9.2",
-    "vitest": "3.2.7"
+    "vitest": "3.2.7",
+    "yaml": "2.9.1"
   },
   "keywords": [
     "cli",