pi-session-continuity 0.1.0

package/CHANGELOG.md

@@ -0,0 +1,13 @@
+# Changelog
+
+## 0.1.0 — 2026-07-09
+
+- Add Pi package manifest for `pi-session-continuity`.
+- Add `/continuity status`, `/continuity checkpoint`, and `/continuity settings` extension entrypoint.
+- Add project-local config validation and trusted-project gating.
+- Add Continuity Brief frontmatter, mandatory heading validation, artifact pathing, failed artifact handling, and disk-backed resume prompt construction.
+- Add automatic threshold check and single-flight duplicate suppression.
+- Add local unit tests and a packaged manual smoke checklist covering the required clean Pi smoke assertions.
+- Add package/docs contract tests for the smoke script and public documentation collateral.
+
+Public tag, GitHub install smoke, npm publish, and external release announcement remain gated by explicit human approval.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Pi Session Continuity contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,172 @@
+# Pi Session Continuity
+
+**Keep long-running Pi coding sessions moving without losing the plot.**
+
+Pi Session Continuity exists so extended agentic coding work can survive the boring failure modes: a context window fills up, a session reloads, a compaction happens, or the next agent has to recover the state of the task. Its job is not to be clever, visible, or exciting. Its job is to be dull enough that you forget it is there — until the moment it quietly gives the next session a reliable handoff.
+
+Only after that intent is clear does the mechanism matter: Pi Session Continuity is a Pi package that writes a structured **Continuity Brief** to disk before it queues any resume prompt. The continuation is driven from the saved artifact, not from fragile in-memory state.
+
+## Why this exists
+
+Long-running agentic coding work often fails at the worst possible boundary: the session is full, the model is tired, the transcript is noisy, and the next prompt has to reconstruct what matters. A normal compaction can reduce tokens, but compaction is still an in-session memory-management step. If the handoff itself fails, or if a reload happens at the wrong time, the recovery story can become ambiguous.
+
+Pi Session Continuity turns that risky boundary into a small, repeatable reliability step:
+
+1. synthesize the current state of the work;
+2. write and validate a disk-backed Continuity Brief;
+3. re-read the saved file;
+4. queue the resume prompt from that exact file;
+5. use native compaction only as token hygiene after the durable path is safe.
+
+Core invariant:
+
+```text
+Durable Continuity Brief first.
+Resume prompt is injected from the disk artifact.
+Compaction is token hygiene, not the source of continuity.
+```
+
+## Why this approach is better for continuous coding
+
+Pi Session Continuity is not trying to be magical or invisible. It is intentionally explicit:
+
+- **Recoverable:** the important state is in a local Markdown artifact that can be inspected, archived, copied, or used by a future Pi session.
+- **Auditable:** every handoff records task, done criteria, constraints, files, validation evidence, open questions, and next actions in a stable structure.
+- **Safer than memory-only continuation:** the resume prompt is generated from the artifact on disk, so continuity does not depend on the agent remembering what it meant to say.
+- **Compatible with compaction:** compaction remains useful, but it is no longer the source of truth for continuity.
+- **Good for unattended work:** if a long task reaches a context threshold, the package can create a visible handoff instead of silently drifting or truncating the useful state.
+
+The result is a conservative infrastructure layer for extended Pi sessions: less clever, more durable, and easier to debug.
+
+## Installation
+
+Recommended install from npm:
+
+```bash
+pi install npm:pi-session-continuity
+```
+
+Pinned GitHub install:
+
+```bash
+pi install git:github.com/bernardofortes/pi-session-continuity@v0.1.0
+```
+
+For local development only:
+
+```bash
+pi -e /path/to/pi-session-continuity
+```
+
+Do not install from sources you do not trust. Pi packages execute with local user permissions.
+
+## Quick start
+
+```text
+/continuity
+/continuity status
+/continuity checkpoint
+```
+
+`/continuity` opens the settings/config menu in interactive Pi TUI sessions. `/continuity checkpoint` performs a full Continuity Handoff: synthesize, validate, write the Continuity Brief, re-read it from disk, and queue the resume prompt from that saved content.
+
+## Commands
+
+- `/continuity` — opens the same settings/config menu as `/continuity settings` in interactive Pi TUI sessions.
+- `/continuity status` — shows a human-readable status panel with enabled/disabled state, trigger and keep percentages, synthesis model and effort, artifact directory, active operation, last checkpoint, last artifact, failures, and stale same-session pending artifacts.
+- `/continuity checkpoint` — manually creates a disk-backed Continuity Brief and queues a resume prompt from it.
+- `/continuity settings` — opens an interactive settings menu in Pi TUI so you can view/change public config values such as `triggerAtPercent` without manually editing JSON. In non-interactive contexts, the same command falls back to textual output.
+
+## Configuration
+
+Project-local config is read only when the project is trusted:
+
+```text
+<workspace>/<CONFIG_DIR_NAME>/session-continuity.json
+```
+
+`CONFIG_DIR_NAME` is supplied by Pi and is normally `.pi`.
+
+Defaults:
+
+```json
+{
+  "enabled": true,
+  "triggerAtPercent": 75,
+  "keepRecentPercent": 20,
+  "synthesisModel": "inherit",
+  "synthesisEffort": "medium",
+  "artifactDirectory": "session-continuity"
+}
+```
+
+`synthesisEffort` controls Continuity Brief synthesis reasoning/thinking level and accepts `inherit`, `minimal`, `low`, `medium`, `high`, or `xhigh`. `artifactDirectory` resolves under `<workspace>/<CONFIG_DIR_NAME>/` unless absolute. Invalid config disables automatic behavior and reports the config path.
+
+In interactive Pi sessions, `/continuity settings` can update this file for the public config fields. In non-interactive contexts, edit the JSON directly or run `/continuity settings` for textual inspection.
+
+## Artifact layout
+
+```text
+<artifactDirectory>/<sessionId>/pending/<eventId>.md
+<artifactDirectory>/<sessionId>/archive/<timestamp>-<eventId>.md
+<artifactDirectory>/<sessionId>/failed/<timestamp>-<eventId>.md
+<artifactDirectory>/<sessionId>/lock/<eventId>.json
+```
+
+Artifacts from other sessions are inert. Same-session stale pending artifacts after reload are reported but not injected automatically.
+
+Successful handoffs are archived per session. After each successful archive, Pi Session Continuity keeps only the newest 10 archived Continuity Briefs for that session and deletes older archived briefs automatically.
+
+## Privacy and security
+
+Continuity Briefs are local files that may contain prompts, tool output, file paths, command results, and sensitive project context. v0.1.0 does not guarantee secret redaction. Choose artifact directories and ignore rules accordingly.
+
+This package must not push, publish, create repositories, upload artifacts, or mutate external systems.
+
+## Manual smoke and release validation
+
+Local package gates:
+
+```bash
+npm test
+npm run typecheck
+npm run smoke:manual
+npm pack --dry-run
+```
+
+`npm run smoke:manual` prints a checklist template for the required clean Pi smoke assertions. The checklist must be executed from a clean Pi install pinned to a GitHub ref before public announcement. Record the Pi version, Node version, OS, install command, smoke transcript, and resulting artifact path.
+
+External validation commands such as `pi install git:github.com/bernardofortes/pi-session-continuity@v0.1.0`, git tags, releases, npm publishing, or uploads require separate explicit human approval.
+
+## Known limitations in v0.1.0
+
+- Local Pi sessions only.
+- No user-facing cleanup command.
+- No cross-machine sync or cloud storage.
+- GitHub clean-install smoke is required before public announcement.
+- npm is the recommended public install path after the tagged release passes smoke validation.
+
+## Troubleshooting
+
+- Invalid config: fix the JSON at the reported path; automatic behavior stays disabled until corrected.
+- Synthesis failure: no resume prompt is queued; inspect the failed artifact path if one was written.
+- Write failure: no resume prompt is queued; fix filesystem permissions or artifact path.
+- Stale pending artifact: `/continuity status` reports it as inert; v0.1.0 will not silently inject it after reload.
+- Untrusted project: trust the project before relying on project-local config or automatic behavior.
+
+## Update / uninstall
+
+```bash
+pi update --extension npm:pi-session-continuity
+pi remove npm:pi-session-continuity
+
+# For pinned GitHub installs:
+pi update --extension git:github.com/bernardofortes/pi-session-continuity@v0.1.0
+pi remove git:github.com/bernardofortes/pi-session-continuity
+```
+
+Removing the package stops loading the extension. Existing local artifacts remain on disk unless you remove them manually.
+
+## Compatibility
+
+Developed against Pi CLI/package APIs from `@earendil-works/pi-coding-agent` 0.80.x, Node.js 22, and Linux. Record exact Pi version, OS, install command, and smoke transcript before tagging a public release.

package/docs/deploys/README.md

@@ -0,0 +1,18 @@
+# SpecForge Deploy Notes
+
+| Date | Scope | Title | Area | Status | Note |
+|---|---|---|---|---|---|
+| 2026-07-07 | SCOPE-0001 | Package Skeleton | Pi package/extension | Done | [deploy-2026-07-07-SCOPE-0001-package-skeleton.md](deploy-2026-07-07-SCOPE-0001-package-skeleton.md) |
+| 2026-07-07 | SCOPE-0002 | Core Artifact Engine Hardening | Artifact/config core | Done | [deploy-2026-07-07-SCOPE-0002-core-artifact-engine.md](deploy-2026-07-07-SCOPE-0002-core-artifact-engine.md) |
+| 2026-07-07 | SCOPE-0003 | Manual Checkpoint Hardening | Manual Continuity Handoff | Done | [deploy-2026-07-07-SCOPE-0003-manual-checkpoint.md](deploy-2026-07-07-SCOPE-0003-manual-checkpoint.md) |
+| 2026-07-07 | SCOPE-0004 | Status/Settings Hardening | Status/settings output | Done | [deploy-2026-07-07-SCOPE-0004-status-settings.md](deploy-2026-07-07-SCOPE-0004-status-settings.md) |
+| 2026-07-07 | SCOPE-0005 | Automatic Threshold Hardening | Automatic threshold trigger | Done | [deploy-2026-07-07-SCOPE-0005-automatic-threshold.md](deploy-2026-07-07-SCOPE-0005-automatic-threshold.md) |
+| 2026-07-07 | SCOPE-0006 | Compaction Hygiene Hardening | Compaction hygiene | Done | [deploy-2026-07-07-SCOPE-0006-compaction-hygiene.md](deploy-2026-07-07-SCOPE-0006-compaction-hygiene.md) |
+| 2026-07-07 | SCOPE-0007 | Tests and Smoke Scripts | Tests and manual smoke collateral | Done | [deploy-2026-07-07-SCOPE-0007-tests-smoke.md](deploy-2026-07-07-SCOPE-0007-tests-smoke.md) |
+| 2026-07-07 | SCOPE-0008 | Public Docs and Release Readiness | Public docs and release-readiness collateral | Done | [deploy-2026-07-07-SCOPE-0008-public-docs-release-readiness.md](deploy-2026-07-07-SCOPE-0008-public-docs-release-readiness.md) |
+| 2026-07-07 | SCOPE-0009 | Dogfood Hardening and Local Readiness | Local v1 readiness decision | Done | [deploy-2026-07-07-SCOPE-0009-dogfood-hardening-local-readiness.md](deploy-2026-07-07-SCOPE-0009-dogfood-hardening-local-readiness.md) |
+| 2026-07-08 | SCOPE-0010 | UX Settings Menu | Status/settings UX | Done | [deploy-2026-07-08-SCOPE-0010-ux-settings-menu.md](deploy-2026-07-08-SCOPE-0010-ux-settings-menu.md) |
+| 2026-07-08 | SCOPE-0011 | Compact Status Footer | Status/footer UX | Done | [deploy-2026-07-08-SCOPE-0011-compact-status-footer.md](deploy-2026-07-08-SCOPE-0011-compact-status-footer.md) |
+| 2026-07-08 | RUN-0012 | Remove Settings Show From TUI | Settings UX | Done | [deploy-2026-07-08-SCOPE-0012-remove-settings-show.md](deploy-2026-07-08-SCOPE-0012-remove-settings-show.md) |
+| 2026-07-08 | RUN-0014 | Status Panel Simplification and Synthesis Effort | Status/settings UX and synthesis config | Done | [deploy-2026-07-08-SCOPE-0014-status-and-effort.md](deploy-2026-07-08-SCOPE-0014-status-and-effort.md) |
+| 2026-07-08 | RUN-0016 | Codex Empty Synthesis Repair | Synthesis reliability | Done | [deploy-2026-07-08-SCOPE-0016-codex-empty-synthesis.md](deploy-2026-07-08-SCOPE-0016-codex-empty-synthesis.md) |

package/docs/deploys/deploy-2026-07-07-SCOPE-0001-package-skeleton.md

@@ -0,0 +1,53 @@
+# Deploy Note: Package Skeleton
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0001
+Run ID: RUN-0001
+Date: 2026-07-07
+Status: Done
+Area: Pi package/extension
+
+## Delivered
+
+- Created the public package skeleton for Pi Session Continuity.
+- Added the `/continuity` extension entrypoint and core config/artifact/handoff helpers.
+- Added tests for config, artifact validation, disk-backed prompt use, failures, stale status, and locks.
+- Added README, CHANGELOG, LICENSE, and smoke checklist scaffold.
+
+## Files touched
+
+- `package.json` / `tsconfig.json` — package metadata and local validation scripts.
+- `extensions/session-continuity/index.ts` — Pi extension command and threshold wiring.
+- `src/` — config, artifact, handoff, constants, and status modules.
+- `test/` — unit coverage for the initial contract.
+- `scripts/smoke/manual-checks.sh` — named manual smoke checklist.
+
+## Evidence
+
+- `npm test` — passed, 4 files and 22 tests (`CMD-0009`).
+- `npm run typecheck` — passed (`CMD-0010`).
+- `npm pack --dry-run` — passed, 11 packaged files (`CMD-0011`).
+- Runtime source grep found no `loop`, `campaign`, or `episode` terms.
+
+## Decisions
+
+- Kept external install/tag/release/publish out of scope.
+- Used project-local config only and `CONFIG_DIR_NAME` for path resolution.
+- Added an extra `.active` lock directory as an atomic local guard while preserving event lock files.
+
+## How it works now
+
+The extension loads config from the trusted project, reports `/continuity status`, and can run a manual or threshold handoff. The handoff writes and validates a pending Continuity Brief, re-reads it from disk for the prompt, marks it injected, archives it, and only then attempts compaction hygiene.
+
+## Future notes
+
+Clean Pi install and live command smoke from a GitHub ref remain required before public release.
+
+## Operational risks
+
+Continuity Briefs may contain sensitive local session context. v0.1.0 does not redact secrets. The `.active` lock is local filesystem coordination only, not cross-machine locking.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0001/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0001/`

package/docs/deploys/deploy-2026-07-07-SCOPE-0002-core-artifact-engine.md

@@ -0,0 +1,39 @@
+# Deploy Note: Core Artifact Engine Hardening
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0002
+Run ID: RUN-0002
+Date: 2026-07-07
+Status: Done
+Area: Artifact/config core
+
+## Delivered
+
+- Hardened Continuity Brief validation for schema version, string identity fields, numeric fields, percentage bounds, and keep/trigger ordering.
+- Enforced the product-spec status state machine for artifact status updates.
+- Restricted resume prompt input to valid `pending` Continuity Brief artifacts only.
+- Rejected relative `artifactDirectory` values that escape `<workspace>/<CONFIG_DIR_NAME>/`; absolute paths remain explicitly allowed.
+- Added focused artifact/config tests for the hardened contract.
+
+## Evidence
+
+- `npm test` — passed, 4 files and 26 tests (`CMD-0003`).
+- `npm run typecheck` — passed (`CMD-0004`).
+- `npm pack --dry-run` — passed (`CMD-0005`).
+- Fresh reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0001`).
+
+## Decisions
+
+- Kept this slice focused on core artifact/config behavior only.
+- Did not change `docs/product-spec.md`.
+- Did not add commands, cleanup behavior, or external install/release steps.
+
+## Operational risks
+
+Clean Pi install and live manual smoke remain release-gated future evidence. The directive-promotion detector remains intentionally heuristic and can be expanded in a later hardening slice if needed.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0002/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0002/`
+- Judge: `specforge/runs/RUN-0002/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-07-SCOPE-0003-manual-checkpoint.md

@@ -0,0 +1,38 @@
+# Deploy Note: Manual Checkpoint Hardening
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0003
+Run ID: RUN-0003
+Date: 2026-07-07
+Status: Done
+Area: Manual Continuity Handoff
+
+## Delivered
+
+- Added focused handoff tests for synthesized validation failure: no resume prompt, failed artifact written, and failed artifact rejected as resume input.
+- Added idle delivery coverage: idle sends immediately without `followUp`; busy still uses `deliverAs: "followUp"`.
+- Strengthened success-path coverage for archive state/path behavior and lock cleanup.
+- Kept implementation unchanged because existing handoff code satisfied the new contract tests.
+
+## Evidence
+
+- `npm test` — passed, 4 files and 28 tests (`CMD-0002`).
+- `npm run typecheck` — passed (`CMD-0003`).
+- `npm pack --dry-run` — passed (`CMD-0004`).
+- Fresh reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0001`).
+
+## Decisions
+
+- Kept this slice focused on manual handoff semantics only.
+- Did not change `docs/product-spec.md`.
+- Did not add status/settings, threshold, or compaction behavior.
+
+## Operational risks
+
+Clean Pi install and live manual smoke remain release-gated future evidence. Exact queued-brief assertion trims trailing whitespace, which preserves substantive disk-sourced content but is not a byte-for-byte newline assertion.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0003/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0003/`
+- Judge: `specforge/runs/RUN-0003/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-07-SCOPE-0004-status-settings.md

@@ -0,0 +1,38 @@
+# Deploy Note: Status/Settings Hardening
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0004
+Run ID: RUN-0004
+Date: 2026-07-07
+Status: Done
+Area: Status/settings output
+
+## Delivered
+
+- Added a reusable settings formatter for the public v0.1.0 config fields.
+- Updated `/continuity settings` to use the shared formatter.
+- Hardened `/continuity status` formatting so untrusted, invalid, enabled, and disabled states all include the complete status field set.
+- Added focused status/settings tests for trust, validity, enabled/disabled config, paths, stale artifacts, and settings fields.
+
+## Evidence
+
+- `npm test` — passed, 4 files and 31 tests (`CMD-0005`).
+- `npm run typecheck` — passed (`CMD-0006`).
+- `npm pack --dry-run` — passed (`CMD-0007`).
+- Fresh delta reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0002`).
+
+## Decisions
+
+- Kept this slice focused on status/settings formatting only.
+- Did not change threshold or compaction behavior.
+- Did not change `docs/product-spec.md`.
+
+## Operational risks
+
+Live Pi command rendering remains covered by source/unit evidence only until a clean Pi smoke run is approved.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0004/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0004/`
+- Judge: `specforge/runs/RUN-0004/subagents/JUDGE-0002.md`

package/docs/deploys/deploy-2026-07-07-SCOPE-0005-automatic-threshold.md

@@ -0,0 +1,37 @@
+# Deploy Note: Automatic Threshold Hardening
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0005
+Run ID: RUN-0005
+Date: 2026-07-07
+Status: Done
+Area: Automatic threshold trigger
+
+## Delivered
+
+- Added a pure automatic-trigger decision helper.
+- Updated `turn_end` to use the helper.
+- Added tests for disabled, untrusted, invalid, unavailable usage/window, below-threshold, and threshold-reached decisions.
+- Verified 65% threshold behavior across 128k and 1M context windows.
+
+## Evidence
+
+- `npm test` — passed, 5 files and 33 tests (`CMD-0002`).
+- `npm run typecheck` — passed (`CMD-0003`).
+- `npm pack --dry-run` — passed (`CMD-0004`).
+- Fresh reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0001`).
+
+## Decisions
+
+- Kept trigger math as `tokens / contextWindow >= triggerAtPercent / 100`.
+- Kept compaction request tied to automatic threshold handoff only; compaction behavior remains a separate episode.
+
+## Operational risks
+
+`turn_end` integration is verified by source inspection and helper tests, not live Pi event smoke.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0005/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0005/`
+- Judge: `specforge/runs/RUN-0005/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-07-SCOPE-0006-compaction-hygiene.md

@@ -0,0 +1,38 @@
+# Deploy Note: Compaction Hygiene Hardening
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0006
+Run ID: RUN-0006
+Date: 2026-07-07
+Status: Done
+Area: Compaction hygiene
+
+## Delivered
+
+- Added focused handoff tests proving compaction is requested only after a successful disk-backed resume path.
+- Verified compaction custom instructions include the archive artifact path and `keepRecentPercent`-derived token count.
+- Added failure-path tests proving validation failure and post-queue archive/update failure do not request compaction.
+- Reconfirmed compaction setup failure remains a warning and does not invalidate archived handoff success.
+
+## Evidence
+
+- `npm test` — passed, 5 files and 35 tests (`CMD-0002`).
+- `npm run typecheck` — passed (`CMD-0003`).
+- `npm pack --dry-run` — passed (`CMD-0004`).
+- Fresh reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0001`).
+
+## Decisions
+
+- Kept compaction as token hygiene only.
+- Did not change runtime implementation because the hardened tests proved the existing behavior.
+- Did not add cleanup or compaction commands.
+
+## Operational risks
+
+Live Pi compaction behavior remains source/test validated only until a clean smoke run is approved.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0006/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0006/`
+- Judge: `specforge/runs/RUN-0006/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-07-SCOPE-0007-tests-smoke.md

@@ -0,0 +1,38 @@
+# Deploy Note: Tests and Smoke Scripts
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0007
+Run ID: RUN-0007
+Date: 2026-07-07
+Status: Done
+Area: Tests and manual smoke collateral
+
+## Delivered
+
+- Updated the package contract to include `scripts` because `smoke:manual` points to a script file.
+- Ensured `package.json` includes `scripts` in package files.
+- Expanded `scripts/smoke/manual-checks.sh` into a runnable manual smoke template with environment fields, all nine required assertions, and pass/fail result columns.
+- Added package/smoke contract tests covering script presence, executable bit, assertion IDs, pass/fail markers, and spec alignment.
+
+## Evidence
+
+- `npm test` — passed, 6 files and 38 tests (`CMD-0002`).
+- `npm run typecheck` — passed (`CMD-0003`).
+- `npm run smoke:manual` — printed the manual checklist (`CMD-0004`).
+- `npm pack --dry-run` — passed and included `scripts/smoke/manual-checks.sh` (`CMD-0005`).
+- Fresh reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0001`).
+
+## Decisions
+
+- Kept clean GitHub-ref install smoke deferred behind explicit approval.
+- Included smoke scripts in packaged files so published package scripts do not reference missing files.
+
+## Operational risks
+
+Clean Pi install and live smoke execution remain release-gated external validation.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0007/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0007/`
+- Judge: `specforge/runs/RUN-0007/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-07-SCOPE-0008-public-docs-release-readiness.md

@@ -0,0 +1,37 @@
+# Deploy Note: Public Docs and Release Readiness
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0008
+Run ID: RUN-0008
+Date: 2026-07-07
+Status: Done
+Area: Public docs and release-readiness collateral
+
+## Delivered
+
+- Expanded README release-validation guidance with local gates, manual smoke checklist usage, and explicit external-action approval gating.
+- Updated CHANGELOG v0.1.0 notes for the packaged manual smoke checklist and docs/package contract tests.
+- Added README and CHANGELOG public-doc contract coverage to `test/package.test.ts`.
+- Reconfirmed MIT license and package metadata through reviewer inspection.
+
+## Evidence
+
+- `npm test` — passed, 6 files and 40 tests (`CMD-0002`).
+- `npm run typecheck` — passed (`CMD-0003`).
+- `npm pack --dry-run` — passed and included public docs/scripts (`CMD-0004`).
+- Fresh reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0001`).
+
+## Decisions
+
+- Kept clean GitHub-ref install smoke deferred behind explicit external-action approval.
+- Did not perform push, tag, release, publish, upload, or repository mutation.
+
+## Operational risks
+
+Clean Pi install and live smoke execution remain required before public tag or announcement.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0008/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0008/`
+- Judge: `specforge/runs/RUN-0008/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-07-SCOPE-0009-dogfood-hardening-local-readiness.md

@@ -0,0 +1,40 @@
+# Deploy Note: Dogfood Hardening and Local Readiness
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0009
+Run ID: RUN-0009
+Date: 2026-07-07
+Status: Done
+Area: Local v1 readiness decision
+
+## Delivered
+
+- Added the local v1 readiness report at `docs/release-readiness/local-v1-readiness-2026-07-07.md`.
+- Ran final local gates for tests, typecheck, manual smoke checklist, package dry-run, and forbidden runtime terminology.
+- Recorded final independent local-readiness review.
+- Preserved the boundary that public release readiness still requires separate human-approved external validation.
+
+## Evidence
+
+- `npm test` — passed, 6 files and 40 tests (`CMD-0002`).
+- `npm run typecheck` — passed (`CMD-0003`).
+- `npm run smoke:manual` — printed manual checklist (`CMD-0004`).
+- `npm pack --dry-run` — passed after final docs (`CMD-0007`).
+- Forbidden runtime terminology grep — no matches after final docs (`CMD-0008`).
+- Fresh reviewer judge — PASS with no blockers/majors and two process minors now addressed (`JUDGE-0001`).
+
+## Decisions
+
+- Local v1 readiness is accepted separately from public release readiness.
+- External clean-install/tag/release validation remains Bernardo-only and requires explicit approval.
+
+## Operational risks
+
+Clean GitHub-ref Pi install/smoke is still required before any public tag or announcement.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0009/autonomous-implementation-packet.yaml`
+- Readiness: `docs/release-readiness/local-v1-readiness-2026-07-07.md`
+- Run: `specforge/runs/RUN-0009/`
+- Judge: `specforge/runs/RUN-0009/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-08-SCOPE-0010-ux-settings-menu.md

@@ -0,0 +1,41 @@
+# Deploy Note: UX Settings Menu
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0010
+Run ID: RUN-0010
+Date: 2026-07-08
+Status: Done
+Area: Status/settings UX
+
+## Delivered
+
+- Updated the product spec to require human-facing status/settings UX and an interactive settings menu.
+- Changed status/settings output to put readable labels first while preserving diagnostic paths and fields.
+- Routed detailed TUI output through a widget with concise headline notifications.
+- Added `/continuity settings show` as the textual fallback.
+- Added interactive `/continuity settings` flows for enabled, trigger threshold, keep percent, synthesis model, and artifact directory.
+- Added project-local config write helpers that validate drafts before writing.
+
+## Evidence
+
+- `npm test` — passed, 43 tests (`CMD-0002`).
+- `npm run typecheck` — passed (`CMD-0003`).
+- `npm pack --dry-run` — passed (`CMD-0004`).
+- Forbidden runtime terminology grep — no matches (`CMD-0005`).
+- Fresh reviewer judge — PASS with no blockers/majors/minors (`JUDGE-0001`).
+
+## Decisions
+
+- Keep the single project-local config source of truth.
+- Keep manual/live TUI navigation as the remaining dogfood validation item; code and tests cover persistence and command fallback.
+- Do not change handoff/artifact semantics in this UX slice.
+
+## Operational risks
+
+Interactive `/continuity settings` navigation should still be manually dogfooded in Pi TUI before removing Pi Continue.
+
+## Artifact refs
+
+- Packet: `specforge/scopes/SCOPE-0010/autonomous-implementation-packet.yaml`
+- Run: `specforge/runs/RUN-0010/`
+- Judge: `specforge/runs/RUN-0010/subagents/JUDGE-0001.md`

package/docs/deploys/deploy-2026-07-08-SCOPE-0011-compact-status-footer.md

@@ -0,0 +1,26 @@
+# Deploy Note: Compact Status Footer
+
+Type: SpecForge Deploy Note
+Scope ID: SCOPE-0011
+Run ID: RUN-0011
+Date: 2026-07-08
+Status: Done
+Area: Status/footer UX
+
+## Delivered
+
+- Removed full multiline status/settings content from the persistent Pi widget path.
+- Added compact footer labels such as `PSC 75/15`.
+- Clear any previous `session-continuity` widget before showing new status.
+- Updated the product spec to forbid persistent oversized status widgets.
+
+## Evidence
+
+- `npm test` — passed, 44 tests (`CMD-0001`).
+- `npm run typecheck` — passed (`CMD-0002`).
+- `npm pack --dry-run` — passed (`CMD-0003`).
+- Forbidden runtime terminology grep — no matches (`CMD-0004`).
+
+## Operational risks
+
+Manual Pi TUI dogfood should confirm the previous truncated widget no longer appears.