Skip to content

fix: write generated guidance as positive instructions #613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chubes4 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: write generated guidance as positive instructions #613

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions guidance/homeboy.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,11 +163,11 @@ Run `homeboy release` or `homeboy deploy` only when the user explicitly asks.
**Control-plane recovery**
Homeboy remains the normal owner of tracked coding work. When Cook cannot admit or run a task:
1. Validate the selected route with `homeboy agent-task cook --preview` using the task's repository, tracker URL, and verification gates.
2. Check `homeboy agent-task providers`, `homeboy status`, and `homeboy runner status`. Use `homeboy agent-task cook --help-full` for the exact configured alternative-route syntax; do not guess provider or runner flags.
2. Check `homeboy agent-task providers`, `homeboy status`, and `homeboy runner status`. Use `homeboy agent-task cook --help-full` for the exact configured alternative-route syntax.
3. Recover an unavailable runner or control-plane service through its documented Homeboy operation, then retry Cook within its configured attempt and provider-rotation budget.
4. After that bounded recovery fails, stop and request explicit operator authorization before invoking a coding runtime directly.

An authorized direct fallback is an exception, not a replacement for Homeboy. Work in an isolated Git worktree linked to the tracker; run and record deterministic verification; then follow the normal commit, push, review, pull-request, and AI-disclosure policy. Record that finalization occurred outside Homeboy and retain the direct runtime command plus session or run evidence with the tracker.
After authorization, complete that fallback in an isolated Git worktree linked to the tracker; run and record deterministic verification; then follow the normal commit, push, review, pull-request, and AI-disclosure policy. Record that finalization occurred outside Homeboy and retain the direct runtime command plus session or run evidence with the tracker. Resume subsequent tracked coding work through Homeboy.

**Discovery**
Use `homeboy --help` and `homeboy <command> --help` for the live command contract. Inspect active configuration with `homeboy config show` and provider readiness with `homeboy agent-task providers`.
Expand Down
6 changes: 3 additions & 3 deletions guidance/wordpress-source.workspace.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,13 @@
guidance_id() { printf 'wordpress-source'; }
guidance_priority() { printf '1'; }
guidance_label() { printf 'WordPress Source'; }
guidance_description() { printf 'Points the agent at the installed WordPress source as read-only reference.'; }
guidance_description() { printf 'Points the agent at the installed WordPress source as reference material.'; }
guidance_freshness() { printf 'static'; }
guidance_conditions() { printf 'Registered by wp-coding-agents on workspace-mode installations.'; }

guidance_render() {
cat <<'MD'
## WordPress Source (Direct Reference, Read-Only)
## WordPress Source (Direct Reference)

The WordPress running this site is on disk underneath you. Read it to verify core APIs, hooks, conventions, and runtime behavior instead of relying on assumptions:

Expand All @@ -28,7 +28,7 @@ The WordPress running this site is on disk underneath you. Read it to verify cor

Grep and read these freely. They are the ground truth for how this site actually behaves.

These paths are **read-only reference**. Make code changes in the configured repository checkout, not in the installed source tree.
Use these paths as reference material. Make code changes in the configured repository checkout.
MD

local repository
Expand Down
2 changes: 1 addition & 1 deletion tests/source-mode.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -393,7 +393,7 @@ SOURCE_MODE=workspace
ENG_PROSE="$(guidance_call wordpress-source render)"
assert_eq "$(guidance_call wordpress-source id)" "wordpress-source" \
"section id is stable across postures"
assert_contains "$ENG_PROSE" "read-only" "workspace mode prose says read-only"
assert_contains "$ENG_PROSE" "reference material" "workspace mode prose treats installed source as reference"
assert_contains "$ENG_PROSE" "configured repository checkout" "workspace mode prose routes changes to the configured repository"

SOURCE_MODE=owned
Expand Down
2 changes: 1 addition & 1 deletion tests/workspace-installation.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ PY

source "$ROOT/guidance/wordpress-source.workspace.sh"
GUIDANCE="$(guidance_render)"
case "$GUIDANCE" in *"read-only reference"*"$REPOSITORY"*) ;; *) fail "workspace guidance did not route to the declared repository" ;; esac
case "$GUIDANCE" in *"configured repository checkout"*"$REPOSITORY"*) ;; *) fail "workspace guidance did not route to the declared repository" ;; esac

printf 'changed\n' >> "$REPOSITORY/plugin.php"
git -C "$REPOSITORY" status --short | grep -q ' M plugin.php' || fail "native Git status did not observe the edit"
Expand Down
Loading