seven->aurora leftover renames (#105)

Author: sneridagh

AGENTS.md

@@ -7,21 +7,21 @@ Each package also has its own `AGENTS.md` with more specific guidance — always
 
 This is a **pnpm monorepo** (`pnpm-workspace.yaml`) containing:
 
-- `apps/seven` — the main Seven (Plone 7) application
-- `packages/*` — shared libraries that make up the Seven stack and tooling
+- `apps/aurora` — the main Plone Aurora application
+- `packages/*` — shared libraries that make up the Plone Aurora stack and tooling
 
 The package manager is **pnpm**. Do not use `npm` or `yarn`.
 
 ## Two Stacks in This Repo
 
-### Seven (Plone 7) — the active stack
+### Plone Aurora — the active stack
 
-Every package except `volto` and `volto-slate` belongs to the **Seven** stack, an API-first, React-based frontend for Plone 7.
-Seven is composed of focused packages that are assembled into `apps/seven`:
+Every package except `volto` and `volto-slate` belongs to the **Plone Aurora** stack, an API-first, React-based frontend for Plone RESTAPI contract (`plone.restapi`).
+Plone Aurora is composed of focused packages that are assembled into `apps/aurora`:
 
 | Layer                      | Packages                                                                            |
 | -------------------------- | ----------------------------------------------------------------------------------- |
-| App shell                  | `apps/seven`                                                                        |
+| App shell                  | `apps/aurora`                                                                        |
 | Public UI (visitor-facing) | `@plone/publicui`, `@plone/layout`, `@plone/blocks`                                 |
 | CMS UI (editor-facing)     | `@plone/cmsui`, `@plone/contents`, `@plone/plate`, `@plone/blocks`, `@plone/layout` |
 | Shared infrastructure      | `@plone/client`, `@plone/registry`, `@plone/react-router`                           |
@@ -32,7 +32,7 @@ Seven is composed of focused packages that are assembled into `apps/seven`:
 ### Volto (Plone 6) — reference only
 
 `packages/volto` and `packages/volto-slate` are the stable Plone 6 frontend.
-They are present **for reference only** during Seven development and will be deleted once they are no longer useful.
+They are present **for reference only** during Plone Aurora development and will be deleted once they are no longer useful.
 Do not make significant changes to these packages.
 
 ## Working in a Package
@@ -79,8 +79,8 @@ pnpm check:ts
 
 ## General Conventions
 
-- **TypeScript** is the default for all new code. Avoid adding plain `.js` files to Seven packages.
-- **Vitest** is the test runner across all Seven packages (not Jest).
+- **TypeScript** is the default for all new code. Avoid adding plain `.js` files to Plone Aurora packages.
+- **Vitest** is the test runner across all Plone Aurora packages (not Jest).
 - **Vite** is the bundler for application code; **tsup** is used for library packages.
 - Keep changes **package-local** unless there is a clear cross-cutting reason.
 - When adding a new package dependency, check whether it already exists in a sibling package or the workspace root before adding it.

packages/agave/AGENTS.md

@@ -4,7 +4,7 @@ This file applies only to `packages/agave` and its subdirectories.
 
 ## What This Package Is
 
-- `@plone/agave` is the **example base theme for Seven** (Plone 7).
+- `@plone/agave` is the **example base theme for Plone Aurora**.
 - It is a CSS-only theme that consumes design tokens and primitives from `@plone/theming`.
 - It is intended as a starting point that end users will most likely **remove and replace** with their own custom theme.
 - TypeScript or React code may be added in the future if needed, but this is not planned — keep it CSS-first.

packages/blocks/AGENTS.md

@@ -4,10 +4,10 @@ This file applies only to `packages/blocks` and its subdirectories.
 
 ## What This Package Is
 
-- `@plone/blocks` provides the **core content blocks for Seven** (Plone 7).
+- `@plone/blocks` provides the **core content blocks for Plone Aurora**.
 - It is **not part of Volto** and not used by it.
 - Each block serves two consumers:
-  - **Edit components** → consumed by `@plone/plate` (the Seven block editor)
+  - **Edit components** → consumed by `@plone/plate` (the Plone Aurora block editor, aka Somersault block editor)
   - **View components** → consumed by `@plone/publicui` (the public-facing renderer)
 
 > [!WARNING]

packages/cmsui/AGENTS.md

@@ -4,7 +4,7 @@ This file applies only to `packages/cmsui` and its subdirectories.
 
 ## What This Package Is
 
-- `@plone/cmsui` is the **full editing and administration UI for Seven** (Plone 7).
+- `@plone/cmsui` is the **full editing and administration UI for Plone Aurora**.
 - It is the interface that content editors use to create, edit, and manage content.
 - It contains routes, widgets, forms, a sidebar, and control panels.
 - The block editor inside `add` and `edit` routes is powered by `@plone/plate`.

packages/cmsui/acceptance/tests/teaser-block.test.ts

@@ -75,7 +75,7 @@ test('Teaser block shows placeholder while source is not selected', async ({
   ).toBeVisible();
 });
 
-test('Teaser block integrates seven object browser trigger in edit mode', async ({
+test('Teaser block integrates Aurora object browser trigger in edit mode', async ({
   page,
 }) => {
   await login(page);

packages/cmsui/components/ControlPanel/ControlPanelsList.tsx

@@ -18,7 +18,7 @@ export const ControlPanelsList = ({
   const addonsControlPanels: ControlPanel[] =
     config.settings.controlpanels || [];
 
-  const sevenControlPanels = [
+  const auroraControlPanels = [
     {
       '@id': '/addons',
       group: t('cmsui.panelgroups.general'),
@@ -72,7 +72,7 @@ export const ControlPanelsList = ({
   ];
 
   let allControlPanels = controlpanels.concat(
-    sevenControlPanels,
+    auroraControlPanels,
     addonsControlPanels,
   );
   // Apply filter function

packages/cmsui/components/VersionOverview/VersionOverview.tsx

@@ -25,12 +25,12 @@ const VersionOverview = ({
   ['@id']: id,
   upgrade,
 }: VersionOverviewProps) => {
-  const sevenVersion = PackageJson.version;
+  const auroraVersion = PackageJson.version;
   return (
     <div className="versionoverview-container">
       <h2>Version Overview</h2>
       <ul>
-        <li>Seven: {sevenVersion}</li>
+        <li>Plone Aurora: {auroraVersion}</li>
         <li>Plone Version: {plone_version}</li>
         <li>CMF Version: {cmf_version}</li>
         <li>Python Version: {python_version}</li>

packages/components/AGENTS.md

@@ -5,15 +5,15 @@ This file applies only to `packages/components` and its subdirectories.
 ## What This Package Is
 
 - `@plone/components` is a thin wrapper layer around `react-aria-components`.
-- Components should be usable out of the box in Seven and in Volto.
+- Components should be usable out of the box in Plone Aurora and in Plone Volto.
 - Keep components presentational and lightweight. Avoid adding app-specific behavior, data logic, or i18n machinery here.
 
 ## Component Model
 
 - Prefer staying very close to the underlying React Aria Components API.
 - Do not reinvent component behavior that RAC already provides.
 - Add Plone value mainly through packaging, small ergonomic wrappers, and styling.
-- Some components, such as `Breadcrumbs`, are intentionally adapted for Seven/Volto and REST API use cases. In those cases, the wrapper props and helpers may shape data for that environment, but the underlying RAC behavior should remain intact.
+- Some components, such as `Breadcrumbs`, are intentionally adapted for Plone Aurora/Volto and REST API use cases. In those cases, the wrapper props and helpers may shape data for that environment, but the underlying RAC behavior should remain intact.
 - Even adapted components should still behave like thin proxies: keep forwarding supported props through to the underlying RAC component so upstream RAC documentation and expectations continue to apply.
 
 ## Two Flavours

packages/contents/AGENTS.md

@@ -4,8 +4,8 @@ This file applies only to `packages/contents` and its subdirectories.
 
 ## What This Package Is
 
-- `@plone/contents` provides the folder contents views for Seven.
-- It is the Seven-specific evolution of Volto's contents view, split into smaller React Aria Components based pieces.
+- `@plone/contents` provides the folder contents views for Plone Aurora.
+- It is the Plone Aurora-specific evolution of Plone Volto's contents view, split into smaller React Aria Components based pieces.
 - Keep the package focused on contents-specific behavior, route wiring, and composition. Do not turn it into a generic component library.
 
 ## Architecture
@@ -32,7 +32,7 @@ This file applies only to `packages/contents` and its subdirectories.
 ## Components
 
 - Components live under `components/` and should remain granular.
-- Prefer package-local components over adding Seven-wide abstractions unless reuse is already proven.
+- Prefer package-local components over adding Plone Aurora-wide abstractions unless reuse is already proven.
 - When touching table cells, actions, or popovers, preserve the shadowing-friendly split between:
   - table/container orchestration
   - per-item rendering

packages/layout/AGENTS.md

@@ -4,7 +4,7 @@ This file applies only to `packages/layout` and its subdirectories.
 
 ## What This Package Is
 
-- `@plone/layout` provides **shared structural layout elements** for Seven.
+- `@plone/layout` provides **shared structural layout elements** for Plone Aurora.
 - It is consumed by both `@plone/cmsui` (editor UI) and `@plone/publicui` (public-facing pages).
 - It contains: page header, footer, breadcrumbs, block renderer (`RenderBlocks`, `SomersaultRenderer`, `BlockWrapper`, `DefaultBlockView`), toast notifications, and slot configuration.