Update docs: getting-started install flow and modernization-plan Phase 7

getting-started.md:
- Replace single-package pip install with two-package install (jupyter_blocks
then jupyter_tidyblocks) in both PyPI and source sections
- Update version numbers to 0.1.0-alpha.0
- Developer workflow: replace `jupyter labextension develop . --overwrite`
with `pip install --no-deps --force-reinstall` after each build

modernization-plan.md:
- Add historical-document note and update title/version to current names
- Add Phase 7: monorepo restructure (packages/blockly → packages/blocks,
new tidyblocks-extension, two Python packages, build fixes)

Co-Authored-By: Claude Sonnet 4.6 <[e-mail]>

docs/getting-started.md

···
 ### From PyPI (once published)
 
 ```bash
+# Tidy data extension (automatically installs jupyter_blocks as a dependency)
 pip install jupyter_tidyblocks
+
+# Or install only the core Blockly editor:
+pip install jupyter_blocks
 ```
 
 ### From source (development install)
···
 git clone https://github.com/teonbrooks/jupyter-blocks.git
 cd jupyter-blocks
 
-# 2. Install the Python package and build the JS packages
-pip install -e ".[dev]"
-jupyter labextension develop . --overwrite
+# 2. Install JavaScript dependencies and build all packages
+npm install
 npm run build
 
-# 3. Verify the extension is registered
+# 3. Install both Python packages in editable mode
+pip install -e ./jupyter_blocks
+pip install -e ./jupyter_tidyblocks
+
+# 4. Verify the extensions are registered
 jupyter labextension list
 ```
 
-You should see a line like:
+You should see lines like:
 
 ```
-jupyter-blocks-extension v0.1.0  enabled  OK  (python, jupyter_blocks)
-jupyter-tidyblocks-extension v0.1.0  enabled  OK  (python, jupyter_tidyblocks)
+jupyter-blocks-extension v0.1.0-alpha.0  enabled  OK  (python, jupyter_blocks)
+jupyter-tidyblocks-extension v0.1.0-alpha.0  enabled  OK  (python, jupyter_tidyblocks)
 ```
 
 ---
···
 npm run watch
 ```
 
-To run unit tests:
+After rebuilding, reinstall the Python packages so the updated labextension
+bundles are deployed to JupyterLab's data directory:
 
 ```bash
-npm test
+pip install --no-deps --force-reinstall -e ./jupyter_blocks
+pip install --no-deps --force-reinstall -e ./jupyter_tidyblocks
 ```
 
-To rebuild and reinstall the labextension into JupyterLab's static assets
-(needed if you change the extension's Module Federation output):
+Then hard-refresh JupyterLab in the browser (`Cmd+Shift+R` / `Ctrl+Shift+R`).
+
+To run unit tests:
 
 ```bash
-jupyter labextension develop . --overwrite
+npm test
 ```

docs/modernization-plan.md

···
-# jupyter-tidyblocks Modernization Plan
+# jupyter-blocks Modernization Plan
+
+> **Historical document.** This plan was written during initial development. Phases 1–6 track the
+> migration from `jupyterlab-blockly` to `jupyter-tidyblocks`. **Phase 7** covers the subsequent
+> monorepo restructure that split the project into two independently installable packages:
+> `jupyter-blocks` (generic Blockly editor) and `jupyter-tidyblocks` (tidy-data layer).
 
 **Base project:** jupyterlab-blockly v0.3.3 (forked from QuantStack/jupyterlab-blockly)
-**Target name:** jupyter-tidyblocks
-**Target version:** 0.1.0
+**Current name:** jupyter-blocks / jupyter-tidyblocks
+**Current version:** 0.1.0-alpha.0
 
 ---
 
···
 - `pyproject.toml` (all path references)
 - `packages/blockly-extension/package.json` (`outputDir`)
 - `turbo.json` (outputs glob)
+
+---
+
+## Phase 7 — Monorepo Restructure: jupyter-blocks + jupyter-tidyblocks ✅
+
+**Status: Complete**
+
+Split the single-package project into two independently installable JupyterLab extensions
+within the same monorepo.
+
+| Before | After |
+|---|---|
+| `packages/blockly/` (`jupyter-tidyblocks`) | `packages/blocks/` (`jupyter-blocks`) |
+| `packages/blockly-extension/` (`jupyter-tidyblocks-extension`) | `packages/blocks-extension/` (`jupyter-blocks-extension`) |
+| — | `packages/tidyblocks-extension/` (new thin wiring plugin) |
+| `jupyter_tidyblocks/pyproject.toml` (root-level) | `jupyter_blocks/pyproject.toml` + `jupyter_tidyblocks/pyproject.toml` |
+
+### Key changes
+
+- **`packages/blocks`**: renamed from `packages/blockly`; `registerTidyblocks` call removed; plugin id `jupyter-blocks:plugin`; file extension `.jpblockly` → `.jblk`; `@jupyterlab/*` and `@lumino/*` moved to `peerDependencies`
+- **`packages/blocks-extension`**: renamed from `packages/blockly-extension`; `outputDir` → `../../jupyter_blocks/labextension`
+- **`packages/tidyblocks-extension`**: new package; thin plugin that calls `registerTidyblocks(registry)` using the `IBlocklyRegistry` token from `jupyter-blocks`
+- **`jupyter_blocks/`**: new Python package; `pyproject.toml` with `hatch-nodejs-version` version source pointing to `packages/blocks-extension/package.json`
+- **`jupyter_tidyblocks/`**: Python package moved out of repo root into subdirectory; depends on `jupyter_blocks`
+
+### Build fixes (also resolved in Phase 7)
+
+- Replaced `jupyter labextension build` with direct `build-labextension` calls to bypass the `jlpm` install step that conflicts with npm workspace symlinks
+- Fixed turbo output declarations: each extension package now has its own `turbo.json` listing only its own labextension output; prevents cache restores from overwriting freshly built artifacts
+- Added `LICENSE` and `README.md` symlinks to each Python package directory for hatchling
+- Added versioned npm override `@jupyterlab/coreutils@<6 → 6.5.6` and `postinstall` cleanup to eliminate `crypto@1.0.1` deprecation warning
+
+### Build system summary (current)
+
+| Package | Build tool | Status |
+|---|---|---|
+| `packages/blocks` | **Vite** library mode | ✅ |
+| `packages/blocks-extension` | **`@jupyterlab/builder ^4.5`** (webpack 5) via `build-labextension` | ✅ |
+| `packages/tidyblocks` | **Vite** library mode | ✅ |
+| `packages/tidyblocks-extension` | **`@jupyterlab/builder ^4.5`** via `build-labextension` | ✅ |
+| Monorepo orchestration | **Turborepo** | ✅ |
 
 ---