Sync accepted GitHop state and prompt records

2026-07-12 01:57:25 +00:00
parent e5bb6a5600
commit b780eadd33
164 changed files with 4811 additions and 12224 deletions
@@ -0,0 +1,64 @@
+# Hop-native Gitea semantics
+
+HopWeb keeps Gitea's existing forge interface and adds a Hop-specific public
+home page, brand mark, and semantic vocabulary for collaboration elements.
+
+## Install
+
+From the project root:
+
+```sh
+./deploy/gitea/install-hop-native.sh
+```
+
+Set `ENV_FILE` when the Compose environment is stored elsewhere:
+
+```sh
+ENV_FILE=/path/to/environment ./deploy/gitea/install-hop-native.sh
+```
+
+The installer copies the home page, brand mark, styles, and adapter into
+Gitea's persistent custom directory, sets the application name to `Hop`,
+restarts Gitea, and waits for a healthy response. Re-run it after editing an
+asset or replacing the Gitea volume.
+
+## Semantic mapping
+
+| Native route and behavior | Hop label |
+| --- | --- |
+| Repository code | Files |
+| — | Prompts (Hop-native causal record) |
+| Issues | Tasks |
+| Branches | Attempts |
+| Commits | Checkpoints |
+| Pull requests | Proposals |
+| Actions | Evidence |
+| Merge pull request | Accept proposal |
+
+The adapter updates visible text, document titles, form placeholders,
+tooltips, and ARIA labels. It scopes replacements to Gitea navigation,
+headings, menus, breadcrumbs, labels, and buttons, so repository content and
+user-authored prose remain unchanged.
+
+Repository home pages also receive a `Hop workflow` group in the existing
+Gitea sidebar. It uses Gitea's own classes, links, icons, and live counts.
+
+## Portable prompt ledger
+
+The Prompts tab reads immutable JSON records from `.hop/records/prompts/`
+directly from the repository branch being reviewed. Hop writes the relevant
+prompt records automatically when it creates a proposal; `make hop-records`
+exports the complete local history on demand. The records include prompts and
+safe review metadata, but deliberately exclude the local Hop database,
+workspaces, check output, and machine paths.
+
+## Upgrade check
+
+After changing the pinned Gitea version:
+
+1. run the installer;
+2. confirm Prompts, Tasks, Proposals, and Evidence in repository navigation;
+3. confirm Attempts and Checkpoints in the Files view;
+4. confirm proposal creation and acceptance labels;
+5. inspect browser console errors; and
+6. test a narrow viewport and keyboard navigation.