Skip to content

Upgrading to 2.0.0

For a fresh checkout, follow Install and initialise. Init selects the required setup. Use this checklist when upgrading a checkout with older operational state.

Install the required CLI

sh
npm install -g @engineering11/e11-foundry@2.0.0
e11 --version

A CLI below minimum_cli_version refuses normal operation with CliVersionTooOld. Install at least the version your project file requires.

Register the checkout

sh
e11 migrate identity bootstrap -d <checkout>

Run once for each checkout. The command creates the local pointer and workspace record. A checkout without earlier runs follows the fresh setup path.

Move existing operational state

sh
e11 migrate storage adopt --workspace <id> -d <checkout>

Use the workspace ID from bootstrap. Adopt selects generation 2 when no legacy run needs relocation. If adopt names existing runs, import their state.

sh
e11 migrate storage import --workspace <id> -d <checkout>

Import relocates the checkout’s runs in every state on this machine. The single-machine path needs no cutover ID or cohort roster. Repeat import after an interrupted relocation to recover.

Pin the Toolkit

sh
e11 migrate toolkit install -d <checkout>

For a local release archive, add --from <tarball>. The command verifies the Toolkit and records its version and digest.

Review and commit shared inputs

Review .foundry/project.toml, .foundry/pricing.json, and .foundry/profiles.toml. Confirm identity, publication root, rates, and meaningful acceptance commands. Init refuses a profile with no acceptance commands.

sh
e11 init
e11 doctor
git add .foundry/project.toml .foundry/pricing.json .foundry/profiles.toml .gitignore
git commit -m "chore: upgrade Foundry inputs"

Resolve fix rows and review price differences. Init removes retired editor skills according to the pinned Toolkit’s removals list.

Select the initiative and import an older board

sh
e11 initiative use <slug>
e11 initiative board import --legacy <path> --title <text>

Board import is for an existing legacy status file. Create a new board with e11 board create for a new initiative.

Update saved prompts

Retired nameUse
e11-platforme11-knowledge
e11-review-adversarial-generale11-review
e11-review-edge-case-huntere11-review
e11-review-verification-gape11-review
e11-review-reachabilitye11-review
e11-review-alloy-auditore11-review
e11-editorial-review-prosee11-review
e11-editorial-review-structuree11-review
e11-sprint-planninge11-sprint
e11-sprint-statuse11-sprint
e11-check-implementation-readinesse11-sprint
e11-dev-storye11-dev-flow
e11-create-storye11-dev-flow
e11-create-prde11-prd
e11-edit-prde11-prd
e11-validate-prde11-prd
e11-create-ux-designe11-ux
e11-create-architecturee11-architecture
e11-create-product-briefe11-product-brief
e11-bootstrap-wizarde11-scaffold
e11-scaffold-appe11-scaffold
e11-scaffold-backende11-scaffold
e11-scaffold-frontend-appe11-scaffold
e11-scaffold-microservicee11-scaffold
e11-scaffold-microservice-packagee11-scaffold
e11-scaffold-sdk-backende11-scaffold
e11-scaffold-sdk-frontende11-scaffold
e11-scaffold-servicee11-scaffold

The former SM role maps to board planning and status through e11-sprint. The former QA role maps to e11-qa-generate-e2e-tests and e11-code-review. Solo development uses e11-spec-flow and e11-dev-flow.

Review translated overrides

Older YAML customizations use TOML overrides now. Review the translation report and each resulting file. Plain arrays append, including principles. Convert unsupported prompts to supported menu entries or persistent facts. Commit team overrides and keep personal files ignored.

Customization explains resolution. Legacy engine compatibility explains old run access.

Coordinated cutover procedures

Proprietary to Engineering11 LLC.