scholaraio

Upgrading To 2.0

ScholarAIO 2.0 marks functional convergence around an All-in-One academic harness for agents. It does not introduce a new runtime data layout for users already on 1.4 or 1.5.

What All-in-One Means In 2.0

All-in-One describes a coherent academic workflow: evidence, persistent state, agent skills, CLI operations, research outputs, and verification live behind one harness. Reasoning and orchestration remain with the active coding agent.

2.x development prioritizes reliability, workflow clarity, cross-agent portability, and user experience. ScholarAIO is not expanding into a general autoresearch platform, a multi-agent framework, or a catalogue of every third-party scientific package.

Upgrade From 1.4 Or 1.5

No data migration is required. Create a backup, update the package from PyPI, and run the normal diagnostics:

python -m pip install --upgrade "scholaraio[full]>=2,<3"
scholaraio setup check
scholaraio index --rebuild

For a source checkout, replace the install command with:

git pull
pip install -e ".[full]"

The final command above must be run from the ScholarAIO repository root.

For a portable recovery point rather than a data-only rsync, configure an instance-scoped target and run it before upgrading. See Configuration for the full backup and restore contract.

Upgrade From 2.0.0 Beta 1

v2.0.0-beta.1 was a GitHub-only prerelease whose installed package metadata already reported 2.0.0. Pip can therefore consider the stable artifact equal to an installed beta. Replace the package explicitly when moving from that prerelease:

python -m pip install --force-reinstall --no-deps "scholaraio==2.0.0"
python -m pip check
scholaraio setup check

For a beta source checkout, fetch the stable tag and reinstall from that clean checkout instead:

git fetch origin --tags
git checkout v2.0.0
python -m pip install -e ".[full]"
scholaraio setup check

Keep the existing runtime backup until the stable installation and index rebuild have both completed successfully.

Upgrade From 1.3 Or Earlier

Complete the explicit 1.4 runtime migration before using normal 2.0 workflows:

scholaraio migrate status
scholaraio migrate upgrade --migration-id upgrade-2.0.0 --confirm
scholaraio migrate verify --migration-id upgrade-2.0.0
scholaraio index --rebuild
scholaraio setup check

Keep an unchanged copy of the old data/, workspace/, and config*.yaml files until migration verification passes. See Upgrading To 1.4 for the full migration and recovery procedure.

Removed Or Narrowed Surfaces

2.x Compatibility Promise

The documented CLI, configuration, runtime layout, skill discovery, persistent identifiers, and published API surfaces follow the ScholarAIO 2.x Public Contract. New work should improve these surfaces without quietly broadening the product into a new platform category.