Top-level directory layout alignment

Question

Align the top-level directory structure with the baseline layout from the repository organization conventions:

.
├── README.md            # Entry point. What this is, how to start, where things are.
├── LICENSE              # Required for anything published.
├── CHANGELOG.md         # Release history, newest first.
├── .gitignore
├── src/                 # Everything shipped.
├── docs/                # Everything explained.
├── tests/               # Everything that proves it works.
├── assets/              # Static inputs: images, templates, fixtures, data files.
├── scripts/             # Automation: build, release, maintenance.
├── dist/                # Build output. Ignored.
└── scratch/             # Disposable working material. Ignored.

Current state has apps/, packages/, docs/, scripts/, build/, node_modules/, .github/, .agents/, .changeset/, plugins/, test-images/, screenshot/, bottomline-proto/.

Decision needed: Which directories from the baseline should exist at the monorepo root vs. inside each package? The conventions say "For a repository with multiple deliverables, repeat the same shape inside each package rather than inventing a second scheme."

Label: wayfinder:task
Part of #2517

Start by comparing the baseline layout in the issue with the current top-level directories and the monorepo packages. Review the repository organization conventions and the discussion in #2517. Done means the root-versus-package directory policy is decided and the resulting layout is documented or agreed before restructuring begins.