feat(discord): git verbs for the Discord Sage on the shared-signals root, seat identity through a package credential helper, vault record protocol (#1509)
Row 24. A writable root that is a git work tree may carry a git object in the binding; the seat then has git_status, git_commit (explicit paths, seat author, Requested-by trailer from the envelope requester, push at once per D6), git_pull (ff-only) and git_push (one branch, never force), plus reserve_id and per-write clone locks under protocol vault. Git children run with no host config and one credential helper, bin/git-credential.mjs, reading the 0600 seat token file named in the binding; the fleet helper serves only the Gitea hosts. Suite 58/58, node 143. rev-code-02 APPROVED round 1 (#1509 comment 26375, tree 82ab962f). Co-Authored-By: Claude Fable 5.1 <[email protected]>
This commit is contained in:
@@ -27,9 +27,12 @@ the envelope's author id is the identity.
|
||||
repository before answering a strategy question; the vault and docs there
|
||||
hold the recorded state. A decision reached in chat is only real once it
|
||||
is written into that repository. When Jason or Carmen asks for a file to
|
||||
be written or changed there, do it with the write tools, then end the
|
||||
reply by naming the file: nothing is committed or shared until Jason
|
||||
commits it from the terminal.
|
||||
be written or changed there, do it with the write tools, then commit it
|
||||
with `git_commit`, naming exactly the files you changed and saying what
|
||||
changed and why; the commit pushes at once. End the reply with the
|
||||
commit hash, and say plainly if the push failed. A new record needs an
|
||||
id from `reserve_id` first, and its registry line goes into the same
|
||||
commit. Never commit a file you did not change.
|
||||
- A read the tools refuse is said plainly. Never guess at a file's contents.
|
||||
|
||||
## Not provided on purpose
|
||||
|
||||
Reference in New Issue
Block a user