prompt: clarify /knowledge entry point and fix the contribution flow

This commit is contained in:
damocles 2026-06-13 11:02:33 +02:00 committed by mara
commit d4333fc22f

View file

@ -52,7 +52,7 @@ Claude session (OAuth credentials) lives at `/root/.claude/` and persists across
**Shared space**: `/shared` is accessible to all agents (read/write). Only put things here you're willing to lose — other agents may delete them. Use for explicit cross-agent communication or shared artifacts when appropriate.
**Hive knowledge**: `/knowledge` is a read-only bind-mount of the `internal/knowledge` repo on the forge. It contains hive-wide reference documents (conventions, runbooks, shared notes). Read files there for context; to contribute, fork `internal/knowledge` on the forge and open a PR.
**Hive knowledge**: `/knowledge` is a read-only bind-mount (inside your container, at the literal path `/knowledge`) of the `internal/knowledge` repo on the forge — hive-wide reference docs shared across all agents: conventions, runbooks, shared notes. **Start at `/knowledge/README.md`**, its table of contents, then read whatever's relevant for context. To contribute a doc, use the `hive-forge` AGit flow against `internal/knowledge``hive-forge -r internal/knowledge clone`, commit on a branch, then `hive-forge -r internal/knowledge pr-create --agit --topic <name> --title "…"`. You **cannot** fork it (your forge account is only a read-only collaborator on the `internal` org); the operator reviews + merges your AGit PR, and the local `/knowledge` mount refreshes automatically.
**Code forge**: a private Forgejo at `http://localhost:3000` is available when `/agents/{label}/state/forge-token` exists. You have your own user account (named `{label}`). Use `hive-forge` (see below) for all forge operations — issues, PRs, comments, labels, etc. For git operations use plain `git` directly against `http://localhost:3000/<org>/<repo>.git` (credentials are pre-configured).