Aimship 0.1.0-preview.24

ITER-023 makes delivery documents more explicit and easier to revise: fixed outlines for eight Markdown artifacts, detailed architecture/sequence/class/data/frontend requirements, complete task and test-case fields, and in-place revision rules that preserve history and visible risks.

• Adds synthetic reservation and applicability examples, plus detailed HTTP, non-HTTP and independent SQL guidance.
• Updates section mapping, case-index references, generated-result locations and approval-boundary regression coverage.
• Breaking delivery compatibility: schema 5 / protocol 3. Protocol-1/2 deliveries (including Preview 17–23) remain intact but cannot be continued or migrated by this release. Complete ongoing deliveries with their supported version, or start a new delivery. The existing bilingual upgrade confirmation protects the installation switch; confirmation does not permit unsupported state writes.

Includes a CRLF heading-parser fix with LF/CRLF regressions for case details, duplicate definitions, original section offsets and read-only behavior. This remains a Preview. Synthetic examples and deterministic tests do not establish real AI-host output quality or a running reservation application. No user installation or real delivery was changed during release.

Validation: macOS Node 26.7.0: 244/244; Windows Node 22/24/26: 244/244 each (run). Documentation: 376 links; package: 76 files. Publication workflow.

Aimship 0.1.0-preview.23

Changes

• Interactive upgrades now explain compatibility in English and Chinese and ask once before switching an incompatible or unverified installation. Only y or Y (with surrounding whitespace ignored) continues; any other answer, Enter, EOF or Ctrl+C cancels and preserves the current installation.
• Noninteractive commands retain structured JSON and the explicit --accept-upgrade-risk option. npm download confirmation does not accept compatibility risk. Accepting an installation switch still cannot bypass delivery protocol checks.
• English and Chinese READMEs describe the three core capabilities and again own upgrade, AI tool registration, version/status, uninstall and troubleshooting commands. The guides focus on delivery steps and examples, with existing links retained.

Delivery protocol 2 / state schema 5 are unchanged. Protocol-1 deliveries, including Preview 17–20, still cannot continue under this workflow; their files are preserved. Finish deliveries that require the old workflow before switching.

Validation and limits

All 236 tests passed on macOS and on Windows with Node 22.23.4, 24.22.2 and 26.13.0, with no failed or skipped tests. The publishing CI also passed all 236 tests. Checks cover 192 documentation links and all 62 distributable files. Native macOS terminal checks cover acceptance, cancellation, EOF and Ctrl+C. These checks do not establish every AI tool/model combination or real delivery acceptance.

This is a Preview release. It does not include the proposed delivery dashboard.

Install or update

npx aimship@latest install

For a first installation, add --host codex, --host cursor or --host claude-code. Reload your AI tool's rules or start a new session after updating.

Aimship 0.1.0-preview.22

This Preview clarifies the shared stage-start and continuation guidance.

• Starting a new execution stage or implementation batch uses its existing prerequisite, approval and authorization checks, with the ordinary active-start save before substantive execution and code changes.
• Readiness for the current design and a successful structural check do not authorize a later implementation stage. Discussion and revisions of a pending design remain design work.
• The same active work, read-only preparation and current-stage document revisions continue normally, without another run or repeated start checks on every action.

This release updates shared guidance while retaining the existing runtime checks, permissions, approval model, fields and commands. Schema 5 / delivery protocol 2 is unchanged from Preview 21; compatible existing deliveries retain their records. Older schema 4 / protocol 1 limitations remain unchanged.

Validated with 218 automated checks on macOS and 218 on each Windows Node 22/24/26 matrix, plus documentation and package checks.

The scenarios and deterministic tool regressions are not a real AI-host replay or a guarantee that every model will avoid workflow drift. This remains a Preview.

Install or update:

npx aimship@latest install

Aimship 0.1.0-preview.21

This Preview gives delivery state one controlled source and clearer stage boundaries.

• Stable business batches are separate from implementation and repair runs. Batch review, overall review, formal verification, document approval and user acceptance retain their own meanings.
• status.md and finite generated summaries in plan, review and testing documents use the same recorded facts. Design, findings and full execution evidence remain readable document content.
• Scoped changes and retests preserve history while reassessing affected work. Repairs do not inflate business-batch counts, and old acceptance does not silently cover reopened engineering work.
• Each implementation batch includes its review and authorized repairs before pausing. After the last batch, Aimship recommends a fresh session for the existing overall review; formal testing remains separate. Project-context guidance and optional host delegation do not add stages, deployment or mandatory agent splitting.

Breaking delivery protocol change: this release uses schema 5 / delivery protocol 2. It cannot continue or re-render schema 4 / protocol 1 deliveries, including Preview 17–20. Existing files are not migrated, rewritten or deleted. Strongly prefer finishing ongoing deliveries with their supported version before upgrading; a new delivery uses the new protocol. Explicit installation risk acceptance permits the software switch only, not unsupported delivery writes.

Validated with 215 automated checks on macOS and 215 on each Windows Node 22/24/26 matrix, plus documentation and package checks.

After upgrading, reload the host rules or start a new session and explicitly use Aimship for the intended new delivery. This is still a Preview; deterministic checks do not prove every AI host/model's behavior or a real complete user delivery.

Install or update:

npx aimship@latest install

Aimship 0.1.0-preview.20

This Preview makes stage execution and delivery progress easier to follow.

• A batch implementation includes its batch review and authorized fixes before pausing. Overall review and formal verification retain separate stops.
• Stage references share clear inputs, scope, actions, outputs and completion conditions. Review modules distinguish batch, overall and repair scope without adding user commands.
• Progress pages show stable stages, artifacts/results and status together. Repairs do not inflate business-batch counts, and applicable retests resolve the current summary while retaining failure history.
• Plan, review and testing records have clearer responsibilities. Numbered document headings retain searchable task, review and test IDs.

Delivery protocol remains 1. Validated preview.17/.18/.19 deliveries retain their documents, progress and effective approvals; no automatic document migration occurs. After upgrading, reload the host rules or start a new session and explicitly use Aimship with the existing delivery directory.

Verified with 183 automated tests on macOS and 183 on each Windows Node 22/24/26 matrix, plus documentation and package checks. These checks do not establish every AI host/model's behavior or a real complete user delivery. This remains a Preview.

Install or update:

npx aimship@latest install

0.1.0-preview.19

• Continue deliveries across compatible software updates with delivery protocol 1 and an exact legacy Preview 17/18 mapping. Normal saves preserve existing documents, valid approvals and progress; session, tool and active-installation bindings still match.
• Explain breaking or unverified installation switches and stop before activation unless explicitly accepted. Installation confirmation does not permit unsupported state writes.
• Make the English/Chinese README explain the delivery value, first request and a clearly illustrative example. Normal installation and upgrades use npx aimship@latest install.
• Support Preview and unsuffixed formal release formats. After the first formal publication, later Previews update only preview, preserving formal latest.

This is a Preview, not formal 0.1.0. Real AI-host/model behavior and complete human Mac/Windows deliveries remain separate validation; tool tests do not guarantee every AI output.

Upgrade after publication with npx aimship@latest install. Save current work, refresh the tool's rules/start a new session, activate Aimship and resume the original delivery directory. Existing completed development does not need to be deleted.

Validation: macOS arm64 / Node26 local tests 173/173; Windows CI Node22/24/26 each 173/173, including compatible legacy-state and installation regressions. Existing workflows are retained; no additional platform support is declared.

Aimship 0.1.0-preview.18

Aimship 0.1.0-preview.18 improves delivery progress and document readability.

• Keep main delivery stages stable across implementation batches and repair reviews; show overall review separately.
• Distinguish unknown or unexecuted results from failed checks, while preserving review and continuation gates.
• Link registered formal artifacts without expanding internal evidence into the progress page.
• Clarify task status in plans, findings/repairs/rechecks in reviews, and design/history/current results in the shared testing document.
• Refine initialization context, design decisions and risk-based test guidance, with updated bilingual guidance and executable synthetic examples.

Validation: 160 deterministic tests passed on macOS and Linux, and on Windows with each of Node 22, 24 and 26. Documentation links, package contents and executable synthetic examples also passed.

This preview retains the HTTP OpenAPI, RPC and independent SQL arrangements. It does not migrate delivery materials. Deterministic checks do not establish model output quality or real AI-tool integration coverage.

Aimship 0.1.0-preview.17

Initialization now records stable delivery context in .aimship/init.md, while status.md retains the full delivery-stage view. The initial receipt includes the delivery directory reminder and the standard delivery endpoint is recorded without another scope-selection question.

New-session suggestions follow major work transitions rather than every saved stop. Skill guidance focuses on results and next actions; open questions stay with their documents and block only work that depends on their answers. Existing document approval, batch review, independent verification and acceptance gates remain in place.

Validation: 156 automated tests, documentation links, complete synthetic examples and package/source byte checks. These checks do not establish real AI-tool session behavior or Windows coverage.

Aimship 0.1.0-preview.16

Changes

• Adopt complete, unchanged user-supplied PRDs and prototypes from the actual delivery request without asking for a repeated document review or recording a fabricated approval. AI-authored or materially revised outputs still require their existing review.
• Distinguish concrete questions from document review and stage continuation in saved status and resume guidance. Preserve downstream approval and change-impact gates.
• Keep normal delivery updates focused on results, artifacts and next actions instead of internal rule quotations. Technical diagnostics and real errors remain available.
• Refine technical-design guidance on business guarantees, critical-path costs and readable cross-system flows, without adding stages, runtime checks or mandatory diagrams.

Validation and limits

Local macOS and Linux CI: 150 tests passed on each. Documentation, complete local synthetic examples and package/source byte checks passed. The npm registry signature and provenance attestation were verified against this exact tag, commit and workflow run. These are program checks, not real AI-session acceptance. Real AI-tool sessions and Windows were not validated for this release.

This preview maintains the existing rules-version write constraint and does not migrate delivery state. For a fresh trial after upgrading, reuse original materials in a new delivery directory. Do not delete just a registered technical document while retaining its old delivery state.

Existing installations can upgrade from the official registry:

npx --registry=https://registry.npmjs.org aimship@0.1.0-preview.16 install
node "$HOME/.aimship/bin/aimship.mjs" --version
node "$HOME/.aimship/bin/aimship.mjs" status

Restart the AI tool and open a new session to load updated rules. The release does not update your local installation automatically.

Aimship 0.1.0-preview.15

This preview simplifies requirement intake and stage handoffs, and makes the generated progress page easier to act on.

• Use one PRD as the requirement authority: directly adopt a complete applicable PRD, write an iteration PRD for partial adoption, or clarify and author one when none exists. Remove the separate Scope stage, document type, template and approval dependency. Prototypes are optional; selected prototype work retains its review gates.
• Start the standard flow without a default delivery-mode questionnaire. Explicit limits and pauses remain respected; starting work grants no blanket approval or permission to merge, deploy or execute database changes.
• Save and stop at each stage boundary. Human-review stages await explicit approval; other stages await continuation without a new approval record. Approval and continuation can be requested together, and a new session is recommended rather than required.
• Put the current stage, review status, user action and delivery directory first in status.md. Show future work as not started and unknown interface/database applicability as pending design, while retaining final completeness checks.
• Preserve current-content approvals and source originals; a revised adopted PRD requires a recorded change and fresh approval. Keep unrelated engineering changes out of business requirements.
• Synchronize the shared Skill, bilingual guides, contributor examples and fixed-version installation examples.

This testing-stage update does not migrate existing delivery state. For a fresh trial, use a new delivery folder with the original PRD/prototype materials and leave the previous delivery untouched.

Validation: 141 automated tests, documentation checks, complete synthetic delivery examples, package checks and actual tarball/source byte comparisons. Real AI-session validation was blocked before model execution by a local app-server permission error; Windows and desktop AI-tool behavior were not verified in this release. State checks and Skill instructions do not control arbitrary external AI tools.