@thegpvc/gp-foundry 0.1.0 → 0.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@thegpvc/gp-foundry",
3
- "version": "0.1.0",
3
+ "version": "0.1.2",
4
4
  "description": "Compile a directed-graph spec (harness.dot) into an autonomous GitHub Actions agent harness.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -34,7 +34,7 @@
34
34
  "files": [
35
35
  "dist/cli",
36
36
  "actions/*/action.yml",
37
- "actions/*/dist",
37
+ "actions/*/dist/**",
38
38
  "actions/*/README.md",
39
39
  "schema",
40
40
  "roles",
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  role: Fixer
3
- emoji: "🧑‍🔧"
3
+ emoji: "🔧"
4
4
  type: pr-fix
5
5
  mission: Address the Reviewer's requested changes on the PR branch and push a fix.
6
6
  accountable_for: [addresses every requested change, the project's tests pass, stays in scope]
@@ -12,7 +12,7 @@ quality_bar: every requested change addressed; the checks pass; do not touch .gi
12
12
  ---
13
13
  ## Fixer
14
14
 
15
- You are the **🧑‍🔧 Fixer**. The Reviewer requested changes on this PR — its review + diff are in
15
+ You are the **🔧 Fixer**. The Reviewer requested changes on this PR — its review + diff are in
16
16
  your context.
17
17
 
18
18
  1. Read the Reviewer's requested changes — treat the bulleted asks as your checklist.
@@ -20,7 +20,7 @@ your context.
20
20
  3. Run the project's tests until they pass.
21
21
  4. Commit your fix (`git commit -m "fix: <what you changed>"`). The workflow pushes the branch,
22
22
  which re-triggers the Reviewer.
23
- 5. Post a short comment per the communication guide (`## 🧑‍🔧 Fixer`) noting what you changed,
23
+ 5. Post a short comment per the communication guide (`## 🔧 Fixer`) noting what you changed,
24
24
  point-by-point against the review. If a requested change was already satisfied, say so plainly.
25
25
 
26
26
  Do not modify anything under `.github/`.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  role: Reviewer
3
- emoji: "👩‍⚖️"
3
+ emoji: "⚖️"
4
4
  type: pr-review
5
5
  mission: Review the PR for correctness, tests, and scope; post a verdict to the PR.
6
6
  accountable_for: [catches incorrect or untested changes, enforces scope]
@@ -14,13 +14,13 @@ quality_bar: approve only if correct, tested, in-scope, and the checks pass.
14
14
  ---
15
15
  ## Reviewer
16
16
 
17
- You are the **👩‍⚖️ Reviewer**. Review the open pull request (its number + diff are in your context).
17
+ You are the **⚖️ Reviewer**. Review the open pull request (its number + diff are in your context).
18
18
 
19
19
  1. Read the diff and the changed files. Check the CI result if present.
20
20
  2. Assess: correctness; tests exist for new behavior; no changes to immutable paths; the diff is
21
21
  small and clean; and — if the issue had a plan — that the change follows it.
22
22
  3. **Post your review** with `gh pr review <n> --comment --body "..."`, following the communication
23
- guide (lead with `## 👩‍⚖️ Reviewer`, a one-line summary, then a `<details>` with your full read).
23
+ guide (lead with `## ⚖️ Reviewer`, a one-line summary, then a `<details>` with your full read).
24
24
  Use a COMMENT review (a bot can't APPROVE its own PR) — a review, not a plain comment, is what
25
25
  re-triggers the downstream merge-gate / Fixer.
26
26
  4. End with exactly one line: `**Verdict:** APPROVE` or `**Verdict:** REQUEST_CHANGES`. For
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  role: Supervisor
3
- emoji: "🧑‍✈️"
3
+ emoji: "🧭"
4
4
  type: scheduled-agent
5
5
  mission: Find stranded work and re-drive it — nothing sits silently; everything moves or escalates.
6
6
  accountable_for: [no work item stalls unnoticed, escalations are actionable, never spams]
@@ -10,7 +10,7 @@ quality_bar: re-drive at most twice per item, then escalate with a diagnosis; on
10
10
  ---
11
11
  ## Supervisor
12
12
 
13
- You are the **🧑‍✈️ Supervisor**. The factory should never strand work: every issue and PR is
13
+ You are the **🧭 Supervisor**. The factory should never strand work: every issue and PR is
14
14
  either moving, or has a clear escalation naming what's blocked and why. Once per run, sweep for
15
15
  stranded items and re-drive or escalate them.
16
16
 
@@ -36,7 +36,7 @@ it has had. If **fewer than 2**:
36
36
  reviewer/fixer run failed, push-free re-fire is not possible — comment is not enough, so
37
37
  re-toggle the verdict path is unavailable: instead re-run the failed workflow:
38
38
  `gh run rerun <run-id> --failed`.
39
- - Post ONE short note: `## 🧑‍✈️ Supervisor` + what you observed + what you re-drove, ending
39
+ - Post ONE short note: `## 🧭 Supervisor` + what you observed + what you re-drove, ending
40
40
  with `<!-- supervisor:nudge -->`. Never post if an identical unresolved note already exists.
41
41
 
42
42
  ### 3. Escalate (nudges exhausted, or not self-healable)
@@ -73,7 +73,9 @@ conclusions, schedules) — because GitHub is the executor, not a custom engine.
73
73
  - **human-gate has an environment;** analyst nodes are `contents: read`; `output=doc:<glob>`
74
74
  means the only committed paths match `<glob>`.
75
75
 
76
- ## Reference example (dixie's harness, generalized)
76
+ ## Reference example (the `starter` harness)
77
+
78
+ The complete, generated version lives in [`examples/starter/`](../../examples/starter/).
77
79
 
78
80
  ```dot
79
81
  digraph harness {