toor/hermes-ui
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
836d0228d25ece235a5bc7f04b7755bb90e4a23b
hermes-ui/docs/harness/README.md
T
toor 1e9ea89d86
Build / build (push) Canceled after 0s
Details
NPM Lockfile Check / npm ci --ignore-scripts (push) Canceled after 0s
Details
Playwright / e2e (push) Canceled after 0s
Details
chore: bootstrap hermes-ui skeleton from 0.6.29 snapshot 
Import the client, server, skills, tests, and build scripts as the starting
point for the rebuild, then trim the surfaces this project does not ship:
Electron desktop packaging, the marketing website, and the ESP32 firmware
tree. CI keeps the web build, e2e, lockfile, release, and Docker workflows.

Rename the package and CLI entry points to hermes-ui, drop the prepare hook so
npm ci no longer triggers a build, and drop the removed tsconfig and nodemon
references. Rewrite AGENTS.md, ARCHITECTURE.md, DEVELOPMENT.md, and the READMEs
so the documented package map and hard rules match this repository.

reference_code/ is ignored: it is a read-only snapshot, not an input to the build.
2026-10-16 10:34:35 +08:00

1.6 KiB
Raw Blame History

Harness Overview

This harness turns recurring project knowledge into files and checks that an agent can discover without chat history.

Goals

  • Make repository context legible through short maps and deeper docs.
  • Keep architecture constraints close to the code they protect.
  • Give agents a deterministic validation path before opening or updating a PR.
  • Prefer mechanical checks over reminder text when a rule can be verified.

Entry Points

  • AGENTS.md is the root map for coding agents.
  • ARCHITECTURE.md documents package boundaries and state ownership.
  • DEVELOPMENT.md remains the contributor rules and command reference.
  • docs/harness/validation.md maps change types to checks.
  • docs/harness/worktree-runbook.md explains isolated worktree development.
  • docs/harness/pr-review.md provides a PR self-review checklist.
  • scripts/harness-check.mjs enforces baseline repository invariants.

Operating Model

  1. Read the root map and the specific doc for the task.
  2. Make the smallest scoped change.
  3. Add or update focused tests when behavior changes.
  4. Run npm run harness:check and the relevant validation commands.
  5. If a failure pattern repeats, improve this harness with docs, tests, scripts, or CI instead of relying on a longer prompt.

What Belongs In The Harness

  • Facts that future agents must know to work safely.
  • Checklists that prevent repeated PR review comments.
  • Scripts that fail fast on repository-wide invariants.
  • Runbooks for local, CI, and release flows.

Do not put long implementation notes in AGENTS.md. Add them under docs/ and link to them from the map.

Reference in New Issue View Git Blame Copy Permalink