admin/homaroma
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

x

Browse Source
This commit is contained in:
Your Name committed 2026-06-28 21:34:58 -04:00
1 parent 3965f4f4da
commit 70877882b0
82 files changed
+4353 -186
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

.agents/orchestrator/BRIEFING.md
+18 -17
View File
@@ -1,19 +1,19 @@
# BRIEFING — 2026-06-28T19:47:00-04:00
# BRIEFING — 2026-06-29T01:20:00Z
## Mission
Implement the `update_category_image` feature in apps/backend and apps/mcp-server.
Orchestrate the implementation of a Premium Mega Menu featuring 3 distinct 1:1 image placements across spa, admin, backend, and website apps.
## 🔒 My Identity
- Archetype: teamwork_preview_orchestrator
- Roles: orchestrator, user_liaison, human_reporter, successor
- Working directory: /home/ti/git/homaroma/.agents/orchestrator
- Original parent: parent
- Original parent conversation ID: 8d1a33c5-564d-44e2-a895-746ca5ea2e5a
- Original parent conversation ID: 7e38829b-163b-46cc-8e49-1748a6bb675b
## 🔒 My Workflow
- **Pattern**: Project Pattern
- **Scope document**: /home/ti/git/homaroma/.agents/orchestrator/PROJECT.md
1. **Decompose**: Decompose the task into Backend implementation (M1), MCP Tool implementation (M2), and E2E & Type Verification (M3).
1. **Decompose**: Decompose the task into E2E Testing Track (M1), DB & Backend Updates (M2), Storefront & Admin UI (M3), and E2E & Adversarial Hardening (M4).
2. **Dispatch & Execute**:
- **Delegate (sub-orchestrator)**: Delegate tasks to specialists (Explorer, Worker, Reviewer, Auditor).
3. **On failure** (in this order):
@@ -25,11 +25,12 @@ Implement the `update_category_image` feature in apps/backend and apps/mcp-serve
- Escalate: report to parent (sub-orchestrators only, last resort)
4. **Succession**: Self-succeed at 16 spawns, write handoff.md, spawn successor.
- **Work items**:
1. M1: Backend Implementation [completed]
2. M2: MCP Tool Implementation [completed]
3. M3: E2E Verification [completed]
- **Current phase**: 4
- **Current focus**: Synthesizing results and reporting back to the parent agent.
1. M1: E2E Testing Track [in-progress]
2. M2: DB & Backend Updates [in-progress]
3. M3: Storefront & Admin UI [in-progress]
4. M4: E2E & Adversarial Hardening [pending]
- **Current phase**: 2
- **Current focus**: Monitoring E2E testing sub-orchestrator and implementation sub-orchestrator.
## 🔒 Key Constraints
- Never write, modify, or create source code files directly.
@@ -38,29 +39,29 @@ Implement the `update_category_image` feature in apps/backend and apps/mcp-serve
- Never reuse a subagent after it has delivered its handoff — always spawn fresh
## Current Parent
- Conversation ID: 8d1a33c5-564d-44e2-a895-746ca5ea2e5a
- Conversation ID: 7e38829b-163b-46cc-8e49-1748a6bb675b
- Updated: not yet
## Key Decisions Made
- Decompose the implementation into M1 (Backend Logic), M2 (MCP Tool), and M3 (Verification).
- Decompose the project into M1 (E2E Testing Track), M2 (DB & Backend Updates), M3 (Storefront & Admin UI), and M4 (Verification/Hardening).
- Spawned E2E Testing Track Orchestrator (2c6cf18b-5304-4783-86d8-2f4836279a4e) and Implementation Track Orchestrator (8e727cf6-d863-41ec-9bd2-f8dead86db2a) to execute both tracks in parallel.
## Team Roster
| Agent | Type | Work Item | Status | Conv ID |
|-------|------|-----------|--------|---------|
| explorer_m1_1 | teamwork_preview_explorer | Explore category routes and MCP indexing | completed | 107f0cb5-2a9c-4545-b0ce-9013039e83ef |
| worker_m1_2 | teamwork_preview_worker | Implement update_category_image feature | completed | 332e146d-3561-4bd1-86f6-d953ad4f79bd |
| reviewer_m1_2 | teamwork_preview_reviewer | Review backend and MCP changes | completed | ce42ff37-298d-4d1c-8de5-b9c5e60fbf13 |
| auditor_m1_2 | teamwork_preview_auditor | Forensic audit of code integrity | completed | 163ce2bd-b9eb-45db-949d-8dffb5f8d2c5 |
| explorer_pre_impl_1 | teamwork_preview_explorer | Pre-implementation investigation | completed | 56f80963-767e-4e4b-ac5a-977badbf0cff |
| sub_orch_e2e | self | E2E Testing Track Orchestrator | in-progress | 2c6cf18b-5304-4783-86d8-2f4836279a4e |
| sub_orch_impl | self | Implementation Track Orchestrator | in-progress | 8e727cf6-d863-41ec-9bd2-f8dead86db2a |
## Succession Status
- Succession required: no
- Spawn count: 4 / 16
- Spawn count: 3 / 16
- Pending subagents: none
- Predecessor: none
- Successor: not yet spawned
## Active Timers
- Heartbeat cron: task-25
- Heartbeat cron: task-83
- Safety timer: none
- On succession: kill all timers before spawning successor
- On context truncation: run `manage_task(Action="list")` — re-create if missing
.agents/orchestrator/ORIGINAL_REQUEST.md
+11
View File
@@ -20,3 +20,14 @@ Please analyze the requirements, build an implementation plan, delegate the task
<ADDITIONAL_METADATA>
The current local time is: 2026-06-28T19:40:31-04:00.
</ADDITIONAL_METADATA>
## 2026-06-29T01:16:56Z
<USER_REQUEST>
You are the Project Orchestrator. Your mission is to orchestrate the implementation of a Premium Mega Menu featuring 3 distinct 1:1 image placements (Root Image on far left, Column Image next to column title, Link Hover Image on far right) across all four HomAroma applications (apps/spa, apps/admin, apps/backend, apps/website) as described in /home/ti/git/homaroma/.agents/ORIGINAL_REQUEST.md.
Your working directory is /home/ti/git/homaroma/.agents/orchestrator.
Please create your plan, progress, and context files under /home/ti/git/homaroma/.agents/orchestrator and coordinate specialists to implement this feature. Report progress and let me know when you are done.
</USER_REQUEST>
<ADDITIONAL_METADATA>
The current local time is: 2026-06-28T21:16:56-04:00.
</ADDITIONAL_METADATA>
.agents/orchestrator/PROJECT.md
+24 -18
View File
@@ -1,29 +1,35 @@
# Project: update_category_image
# Project: Premium Mega Menu
## Architecture
- Database Schema: `Category` model in Prisma has an `imageUrl` field.
- Backend API: `apps/backend/src/routes/categories.ts` handles category operations.
- MCP Server: `apps/mcp-server/index.ts` exposes MCP tools to agents.
- **Database Schema**: Update `Menu` and `MenuItem` models in Prisma schema (`apps/backend/prisma/schema.prisma`) to support `rootImage`, `columnImage`, and `hoverImage` fields.
- **Backend API**: `apps/backend/src/routes/menus.ts` handles saving and loading the menu tree payload and database fields.
- **MCP Server**: `apps/mcp-server/index.ts` and tool suite handles querying, modifying, and auditing menu structure.
- **Admin Panel UI**: `apps/admin/src/pages/MenuManagerPage.tsx` and `apps/spa/src/components/DesktopMegaMenu.tsx` / `MobileDrawer.tsx` allow configuring and rendering the 3-image layout.
- **Storefront UI**: `apps/website/src/components/navigation/DesktopMegaMenu.tsx` / `MobileDrawer.tsx` render the 3-image layout using `next/image` with lazy loading and fade-in micro-animations.
## Milestones
| # | Name | Scope | Dependencies | Status |
|---|------|-------|-------------|--------|
| M1 | Backend Implementation | Expose `PATCH /api/categories/:id/image` in `apps/backend/src/routes/categories.ts` | None | DONE |
| M2 | MCP Tool Implementation | Add `update_category_image` tool schema and handler in `apps/mcp-server/index.ts` | M1 | DONE |
| M3 | Verification & Auditing | Compile the monorepo, test the tool end-to-end, and run Forensic Auditor. | M2 | DONE |
| M1 | E2E Testing Track | Create requirement-driven E2E tests for the 3-image mega menu layout. | None | PLANNED |
| M2 | DB & Backend Updates | Prisma migration, backend routes & schemas, and MCP tools updates. | None | PLANNED |
| M3 | Storefront & Admin UI | Implement admin configuration UI and Next.js storefront image rendering. | M2 | PLANNED |
| M4 | E2E & Adversarial Hardening | Pass E2E tests, add adversarial tests, run integrity audit. | M1, M3 | PLANNED |
## Interface Contracts
### Backend API
- `PATCH /api/categories/:id/image`
- Body: `{ imageUrl: string }`
- Response: Updated Category object
### Database Schema
- `Menu` model: `rootImage String?`
- `MenuItem` model: `columnImage String?`, `hoverImage String?`
### MCP Tool Schema
- Name: `update_category_image`
- Input Schema:
- `id`: number (required)
- `imageUrl`: string (required)
### MegaMenuPayload Type Definitions
- `MegaMenuPayload`: `{ rootImage?: string; ... }`
- `MenuColumn`: `{ columnImage?: string; ... }`
- `MenuLink`: `{ hoverImage?: string; ... }`
## Code Layout
- Backend routes: `apps/backend/src/routes/categories.ts`
- MCP server: `apps/mcp-server/index.ts`
- **Database**: `apps/backend/prisma/schema.prisma`
- **Shared Types**: `packages/types/index.ts`
- **Backend Routes**: `apps/backend/src/routes/menus.ts`
- **MCP Server**: `apps/mcp-server/menu-tools.ts`, `apps/mcp-server/menu-toolkit.ts`
- **Admin UI**: `apps/admin/src/pages/MenuManagerPage.tsx`
- **SPA UI**: `apps/spa/src/components/DesktopMegaMenu.tsx`, `apps/spa/src/components/MobileDrawer.tsx`, `apps/spa/src/store/menuStore.ts`
- **Website UI**: `apps/website/src/components/navigation/DesktopMegaMenu.tsx`, `apps/website/src/components/navigation/menuTypes.ts`
.agents/orchestrator/plan.md
+26 -16
View File
@@ -1,20 +1,30 @@
# Execution Plan: Update Category Image Feature
# Execution Plan: Premium Mega Menu
## Step 1: Codebase Exploration and detail verification
- Target: Run an Explorer to verify category routes in `apps/backend` and existing MCP tools in `apps/mcp-server`.
- Verification: Explorer reports on exact files, routes, schemas, and confirms where categories are defined, where the database models are, and how other MCP tools interface with the backend.
## Step 1: E2E Testing Track (M1)
- Target: Spawn an E2E testing sub-orchestrator to write requirement-driven E2E tests for the 3-image layout Mega Menu.
- Verification: Tests cover:
- Root Image on the left.
- Column Image inside grid next to/above column title.
- Hovering links displaying the correct link image on the right.
- Lazy loading of hover images.
- Responsive layout (mobile drawer hides complex image layouts gracefully).
## Step 2: M1 - Backend Implementation
- Target: Implement the PATCH endpoint `PATCH /api/categories/:id/image` in `apps/backend/src/routes/categories.ts` to update the `imageUrl` of a category.
- Verification: Worker runs typecheck and build in `apps/backend`.
## Step 2: Database & Backend Updates (M2)
- Target: Spawn database and backend lead agents to:
- Add optional `rootImage` to `Menu`, and `columnImage`, `hoverImage` to `MenuItem` in `apps/backend/prisma/schema.prisma`.
- Create and run migration.
- Update `packages/types/index.ts` to include the three image fields.
- Update Elysia route body validation schemas and database saving logic in `apps/backend/src/routes/menus.ts`.
- Update `apps/mcp-server/menu-tools.ts` and `menu-toolkit.ts` if needed.
- Verification: Monorepo compiles successfully (`npm run typecheck` and builds pass).
## Step 3: M2 - MCP Tool Implementation
- Target: Add `update_category_image` tool definition in `apps/mcp-server/index.ts` to accept `id` (number) and `imageUrl` (string). Implement the handler to call the backend endpoint `PATCH /categories/:id/image`.
- Verification: Worker runs typecheck and build in `apps/mcp-server`.
## Step 3: Storefront & Admin UI (M3)
- Target: Spawn frontend lead and Next.js SEO architect agents to:
- Update the admin builder `apps/admin/src/pages/MenuManagerPage.tsx` to support configuring `rootImage`, `columnImage`, and `hoverImage` inside the tree node editor.
- Update `apps/spa/src/store/menuStore.ts` and `apps/spa/src/components/DesktopMegaMenu.tsx` / `MobileDrawer.tsx` to use the new fields.
- Update `apps/website/src/components/navigation/menuTypes.ts` and `apps/website/src/components/navigation/DesktopMegaMenu.tsx` / `MobileDrawer.tsx` to implement the 3-image layout using `next/image` with lazy loading and fade-in animations.
- Verification: No typecheck errors and UI renders correctly based on configured values.
## Step 4: M3 - E2E Verification & Auditing
- Target:
- Run typecheck and build across the monorepo to ensure compilation.
- Verify `update_category_image` tool registers on the MCP server.
- Run a script or test to confirm that calling the tool successfully updates a category's `imageUrl` in the database.
- Execute Forensic Auditor to verify code integrity and no cheating.
## Step 4: E2E & Adversarial Hardening (M4)
- Target: Run E2E tests, add white-box/adversarial tests (Phase 2), and run the Forensic Auditor to audit code integrity.
- Verification: All tests pass, Forensic Auditor gives a CLEAN verdict.
.agents/orchestrator/progress.md
+9 -11
View File
@@ -1,17 +1,15 @@
## Current Status
Last visited: 2026-06-28T19:47:00-04:00
- [x] Initialized workspace and briefing
- [x] Planning (creating plan.md and PROJECT.md)
- [x] Spawning Explorer to analyze codebase for category routes and MCP tools
- [x] M1: Backend implementation (completed)
- [x] M2: MCP tool registration & handling (completed)
- [x] M3: Verification & Auditing (completed)
Last visited: 2026-06-29T01:20:00Z
- [x] Initialized plan.md and PROJECT.md for Premium Mega Menu
- [x] Explored codebase and analyzed current menu architecture
- [x] Initialized subagent folders for implementation and E2E testing tracks
- [ ] M1: E2E Testing Track (not started - dispatching sub-orchestrator)
- [ ] M2: Database & Backend Updates (not started)
- [ ] M3: Storefront & Admin UI (not started)
- [ ] M4: E2E & Adversarial Hardening (not started)
## Iteration Status
Current iteration: 1 / 32
## Retrospective Notes
- The database schema and shared types already supported the category imageUrl field, so we did not need to run migrations.
- Adding a dedicated patch endpoint `PATCH /categories/:id/image` allows a scoped, minimal payload update for categories.
- Reviewer recommended adding adminOnly middleware, which is pre-existing security technical debt across all categories modification endpoints in the app. However, this is outside the current scope and should be addressed in a security hardening ticket.
- Integration tests directly exercising Elysia routes and MCP JSON-RPC protocol ensure long-term stability and regression testing.
- Explorer report completed. Located types in `packages/types/index.ts`, recursive layouts in SPA/website, routes in `menus.ts`, and lack of image controls in admin page builder.