board-viewer/.wiki/CLAUDE.md

Wiki Schema — board-viewer

Project-specific wiki conventions. Read this before any wiki operation.

This wiki follows Karpathy's LLM Wiki pattern: https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f

The using-wiki skill enforces the workflow and file formats. This file overrides the skill where they conflict.

Page types

• entities/ — discrete things this project tracks (people, services, modules).
• concepts/ — recurring ideas, design decisions, gotchas.
• packages/ — code packages this project produces or consumes.
• sources/ — one summary page per ingested external doc; carries ingested: and raw_path:.
• overview.md — single project-wide overview.

Naming

• kebab-case.md, Latin only. Transliterate Cyrillic in filenames; keep the original title in the H1 + frontmatter.

Domain conventions

Mandatory: read design context before implementation

Before picking up any task in .tasks/, load the full design context. It does not live in this repo fully — only pointers do. Sources, in order:

1. Canonical design: .wiki/concepts/board-viewer.md. Architecture decisions, scope, MVP feature list, anti-patterns (hermes-style, Gitea Projects), trade-offs.
2. Brainstorm process trace (rationale): ~/projects/.workshop/.archive/2026-05-22-board-viewer.md. Why each decision was made, what was rejected and why, clarifying note that mcp__projects-meta__* is not callable from HTTP service.
3. Local overview.md — quick orientation summary; never source of truth.

Do not invent thresholds, taxonomies, container topology, or pipeline stages from task where_stopped lines alone — those are pointers, not specifications.

TDD posture

Per follow tdd-criteria trigger in this CLAUDE.md: impl-tasks board-viewer-gitea-reader and board-viewer-html-render are TDD. board-viewer-cron-deploy falls under the infrastructure carve-out (declarative systemd / traefik / DNS — verify by deploy + curl, not unit tests). Mark each impl commit accordingly.