Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .claude.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@
"provenance": {
"generator": "scripts/build-cognitive-manifest.py",
"repository": "Aegis-Omega/AEGIS-OMEGA",
"source_ref": "feat/automaton-3-sovereign-execution",
"parent_state_hash": "37ec8f38ff2453dcd59c292f3c865a5ddeb893b5dadc52a80a06762d2b6982da",
"source_ref": "feat/production-cookbook-dashboard",
"parent_state_hash": "410bcd49c721e65050382ae759db7af2f41fa9f572e625174252c72a8748ea93",
"signature_mode": "GITHUB_OIDC_ATTESTATION"
},
"hashing": {
Expand Down Expand Up @@ -488,5 +488,5 @@
"on_success": "broadcast-attested-verified-event-stream"
}
},
"state_hash": "410bcd49c721e65050382ae759db7af2f41fa9f572e625174252c72a8748ea93"
"state_hash": "abf4dea0875a2d6e1dd9865288b21ba6ece57ed7d05ed9ffc797e9b57ad6148f"
}
5 changes: 4 additions & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,10 @@
"workspaces": ["backend"],
"scripts": {
"dev-backend": "npm run dev --prefix backend",
"dev": "npm run dev-backend"
"dev": "npm run dev-backend",
"dev:batchbook": "npm run dev --prefix production-cookbook",
"build:batchbook": "npm run build --prefix production-cookbook",
"preview:batchbook": "npm run preview --prefix production-cookbook"
Comment on lines +7 to +9

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

2. Batchbook scripts won't run 🐞 Bug ☼ Reliability

The new root scripts (dev:batchbook/build:batchbook/preview:batchbook) run `npm ... --prefix
production-cookbook, but a standard repo-root npm ci/install` will not install
production-cookbook dependencies because it is not part of the root workspace set, so these
scripts can fail with missing vite/React modules on a clean checkout.
Agent Prompt
### Issue description
Root-level scripts invoke `production-cookbook` via `--prefix`, but the repo-root install does not install `production-cookbook/node_modules` because it is not part of the root workspace set. This makes `npm run dev:batchbook` / `build:batchbook` / `preview:batchbook` unreliable on a clean checkout.

### Issue Context
- Root `package.json` only lists `backend` in `workspaces`.
- The new scripts run in `production-cookbook/`, which has its own `package.json` and dependencies.

### Fix
Choose one:
1) **Recommended:** add `production-cookbook` to root `workspaces` and regenerate the **root** `package-lock.json` so `npm ci` at the repo root installs it.
2) Alternatively, make the root scripts install before running, e.g. `npm ci --prefix production-cookbook && npm run dev --prefix production-cookbook` (slower, but self-contained).

### Fix Focus Areas
- package.json[1-10]
- package-lock.json[6-15]
- production-cookbook/package.json[1-20]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Comment on lines +7 to +9

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Make Batchbook root scripts install their deps

In a fresh checkout where contributors run the normal root install, these new root entrypoints don't have Batchbook's dependencies available because production-cookbook is not included in the root workspaces (the workspace list is still only backend) and the root lockfile does not include it. I verified the root entrypoint exits with sh: 1: vite: not found when production-cookbook/node_modules is absent, so the advertised npm run build:batchbook/dev/preview commands require an undocumented second install inside the subdirectory. Please add this app to the root workspace/update the root lock, or make the scripts bootstrap/use the subproject dependencies explicitly.

Useful? React with 👍 / 👎.

},
"devDependencies": {
"concurrently": "latest"
Expand Down
15 changes: 15 additions & 0 deletions production-cookbook/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="theme-color" content="#063969" />
<meta name="description" content="Batchbook production management dashboard" />
<link rel="icon" href="/favicon.svg" type="image/svg+xml" />
<title>Batchbook — Production overview</title>
</head>
<body>
<div id="root"></div>
<script type="module" src="/src/main.jsx"></script>
</body>
</html>
Loading