Create arch-landing-site and arch-claude-custom architecture notes in pal-e-docs #236

New issue

Open

opened 2026-04-04 22:55:43 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-04-04 22:55:43 +00:00

Contributor

Type

Feature

User Story

story:superuser-manage As superadmin, I want architecture notes to back every arch:X board label so that the traceability triangle is complete.

Lineage

Story: story:superuser-manage
Arch: arch:claude-custom
Blocked by: Nothing
Blocks: Nothing (documentation gap, not functional)

Repo

forgejo_admin/claude-custom (but work is in pal-e-docs via MCP, not code)

Context

Multiple QA reviews flagged two missing architecture notes:

arch-landing-site — referenced by 6+ board items on board-westside-basketball (schedule tickets, etc). No backing note.
arch-claude-custom — referenced by board items on board-pal-e-agency. No backing note.

These are pal-e-docs notes (created via mcp__pal-e-docs__create_note), not code files. They document the architecture of the westside-landing SvelteKit app and the claude-custom hooks/skills repo respectively.

File Targets

pal-e-docs note: arch-landing-site — westside-landing SvelteKit architecture (routes, auth, API proxy, deployment)
pal-e-docs note: arch-claude-custom — claude-custom architecture (hooks, skills, agents, settings, keybindings)

Acceptance Criteria

arch-landing-site note exists in pal-e-docs with project westside-basketball
arch-claude-custom note exists in pal-e-docs with project pal-e-agency
Both follow the architecture note pattern (see arch-domain-westside-basketball for reference)
Board items with arch:landing-site and arch:claude-custom labels have backing notes

Test Expectations

mcp__pal-e-docs__get_note(slug="arch-landing-site") returns content
mcp__pal-e-docs__get_note(slug="arch-claude-custom") returns content

Constraints

Use Dottie agent (doc librarian) — no code changes
Follow existing arch note patterns

Checklist

Create arch-landing-site note with SvelteKit route structure, auth flow, API proxy
Create arch-claude-custom note with hooks taxonomy, skills structure, agent definitions
Verify notes are discoverable via list_notes(tags="architecture")

arch-domain-westside-basketball (reference pattern)
arch-auth-westside-basketball (reference pattern)
review-808-2026-04-04 (flagged arch-landing-site missing)
review-820-2026-04-04 (flagged arch-claude-custom missing)

### Type Feature ### User Story `story:superuser-manage` As superadmin, I want architecture notes to back every `arch:X` board label so that the traceability triangle is complete. ### Lineage - **Story:** `story:superuser-manage` - **Arch:** `arch:claude-custom` - **Blocked by:** Nothing - **Blocks:** Nothing (documentation gap, not functional) ### Repo `forgejo_admin/claude-custom` (but work is in pal-e-docs via MCP, not code) ### Context Multiple QA reviews flagged two missing architecture notes: - `arch-landing-site` — referenced by 6+ board items on board-westside-basketball (schedule tickets, etc). No backing note. - `arch-claude-custom` — referenced by board items on board-pal-e-agency. No backing note. These are pal-e-docs notes (created via `mcp__pal-e-docs__create_note`), not code files. They document the architecture of the westside-landing SvelteKit app and the claude-custom hooks/skills repo respectively. ### File Targets - pal-e-docs note: `arch-landing-site` — westside-landing SvelteKit architecture (routes, auth, API proxy, deployment) - pal-e-docs note: `arch-claude-custom` — claude-custom architecture (hooks, skills, agents, settings, keybindings) ### Acceptance Criteria 1. `arch-landing-site` note exists in pal-e-docs with project `westside-basketball` 2. `arch-claude-custom` note exists in pal-e-docs with project `pal-e-agency` 3. Both follow the architecture note pattern (see `arch-domain-westside-basketball` for reference) 4. Board items with `arch:landing-site` and `arch:claude-custom` labels have backing notes ### Test Expectations - `mcp__pal-e-docs__get_note(slug="arch-landing-site")` returns content - `mcp__pal-e-docs__get_note(slug="arch-claude-custom")` returns content ### Constraints - Use Dottie agent (doc librarian) — no code changes - Follow existing arch note patterns ### Checklist - [ ] Create `arch-landing-site` note with SvelteKit route structure, auth flow, API proxy - [ ] Create `arch-claude-custom` note with hooks taxonomy, skills structure, agent definitions - [ ] Verify notes are discoverable via `list_notes(tags="architecture")` ### Related - `arch-domain-westside-basketball` (reference pattern) - `arch-auth-westside-basketball` (reference pattern) - review-808-2026-04-04 (flagged arch-landing-site missing) - review-820-2026-04-04 (flagged arch-claude-custom missing)