goalbuddy 0.3.6 → 0.3.7

package/examples/github-pr-workflow-extension/pr-handoff.md

@@ -1,46 +0,0 @@
-# PR Handoff: Add GitHub PR Workflow Extension
-
-## Suggested Title
-
-Add GitHub PR workflow extension
-
-## Summary
-
-- Adds `github-pr-workflow` as a cataloged Goal Maker extension.
-- Documents a local-first workflow for turning goal receipts into GitHub PR handoff text.
-- Keeps `state.yaml` authoritative and treats GitHub PR content as generated review context.
-
-## Goal Context
-
-- Original request: `$goal-maker add a new extension to goal-maker`
-- Target outcome: a discoverable GitHub PR workflow integration extension with catalog metadata, docs, and example proof.
-- Completion proof: catalog entry, extension documentation, example artifact, and local checks.
-
-## Changed Files
-
-- `extend/catalog.json`
-- `extend/README.md`
-- `extend/github-pr-workflow/README.md`
-- `extend/github-pr-workflow/extension.yaml`
-- `examples/github-pr-workflow-extension/pr-handoff.md`
-- `README.md`
-
-## Verification
-
-```bash
-node internal/cli/goal-maker.mjs extend --catalog-url extend/catalog.json --json
-node internal/cli/goal-maker.mjs extend github-pr-workflow --catalog-url extend/catalog.json --json
-node internal/cli/goal-maker.mjs extend install github-pr-workflow --catalog-url extend/catalog.json --dry-run --json
-npm run check
-git diff --check
-```
-
-## Review Notes
-
-- This is a local handoff workflow, not live GitHub automation.
-- No GitHub token is required for discovery, details, or install dry-run.
-- Future live PR creation should be a separate extension or explicitly approved follow-up task.
-
-## Follow-Up
-
-- Consider a later command or template generator only after the cataloged workflow proves useful.

package/goalbuddy/extend/github-projects/README.md

@@ -1,105 +0,0 @@
-# GitHub Projects
-
-Mirror a GoalBuddy `state.yaml` board into GitHub Projects without making GitHub the source of truth.
-
-This extension ports the GitHub Projects work from PR #1 into the catalog-based extension system. It keeps the package core dependency-free and optional, while giving teams a practical way to publish a GoalBuddy board into a familiar project surface.
-
-## Use When
-
-- A long-running GoalBuddy board needs stakeholder visibility in GitHub Projects.
-- A team wants one-way sync from `state.yaml` into ProjectV2 draft issues.
-- The PM needs a dry-run plan before using GitHub credentials.
-- Existing GoalBuddy receipts, verification commands, allowed files, owners, and dependencies should be visible in a board layout.
-
-## What It Creates
-
-The live sync ensures a GitHub Project has:
-
-- Draft issues keyed by `Task ID`, so reruns update existing cards instead of duplicating them.
-- Status mapping: `queued -> Todo`, `active -> In Progress`, `blocked -> Blocked`, `done -> Done`.
-- Single-select fields for `Status`, `Priority`, `Work Type`, and `Agent Lane`.
-- Text fields for `Task ID`, `Owner`, `Goal Role`, `Agent Responsible`, `Credential Gate`, `Parent ID`, `Depends On`, `Receipt Summary`, `Verify`, `Allowed Files`, and `Goal Updated`.
-- A `Goal Board` board-layout view for PM flow.
-
-The extension must use the bundled sync script for live writes. Do not use Computer Use, browser automation, or the GitHub web UI to create or repair the board view. Do not replace the script with `gh project` commands; `gh project` does not expose the complete ProjectV2 view creation path this extension needs. The script uses GitHub GraphQL for projects, fields, items, and draft issues, plus the GitHub REST Project views endpoint for the `Goal Board` view.
-
-The sync only creates or reuses `Goal Board`. It does not create a default Table view, an `Agent Workboard`, or extra role-specific views. GitHub may still show views that already existed on the Project.
-
-The extension does not promise custom board grouping or sort order. GitHub's public Project views REST API currently accepts `name`, `layout`, `filter`, and `visible_fields` when creating a view, and GraphQL exposes grouping/sort fields for reading but not a public mutation for saving them. Because that display state cannot be written reliably through the public API, the sync only creates supported fields, cards, and the single `Goal Board` view.
-
-## Inputs
-
-- `docs/goals/<slug>/state.yaml`
-- Optional `GITHUB_PROJECT_ID`
-- Optional `GITHUB_PROJECT_OWNER` and `GITHUB_PROJECT_NUMBER`
-- `GITHUB_TOKEN` or `GH_TOKEN` for live sync
-
-## Dry Run
-
-Dry-run mode does not call GitHub:
-
-```bash
-node extend/github-projects/scripts/sync-github-project.mjs \
-  --state docs/goals/<slug>/state.yaml \
-  --dry-run
-```
-
-For structured output:
-
-```bash
-node extend/github-projects/scripts/sync-github-project.mjs \
-  --state docs/goals/<slug>/state.yaml \
-  --dry-run \
-  --json
-```
-
-## Live Sync
-
-Always run the bundled script for live sync. It creates or reuses the `Goal Board` view as part of the same run that syncs fields and draft issues.
-
-Use a ProjectV2 node ID:
-
-```bash
-GITHUB_TOKEN=... node extend/github-projects/scripts/sync-github-project.mjs \
-  --state docs/goals/<slug>/state.yaml \
-  --project-id <project-node-id>
-```
-
-Or use an owner and project number:
-
-```bash
-GITHUB_TOKEN=... node extend/github-projects/scripts/sync-github-project.mjs \
-  --state docs/goals/<slug>/state.yaml \
-  --owner <user-or-org> \
-  --project-number <number>
-```
-
-Environment alternatives:
-
-- `GITHUB_PROJECT_ID`
-- `GITHUB_PROJECT_OWNER`
-- `GITHUB_PROJECT_NUMBER`
-- `GITHUB_TOKEN` or `GH_TOKEN`
-
-## Verification
-
-```bash
-node --test extend/github-projects/test/*.test.mjs
-node extend/github-projects/scripts/sync-github-project.mjs \
-  --state extend/github-projects/examples/goal-board-sync/state.yaml \
-  --dry-run
-node extend/github-projects/scripts/sync-github-project.mjs \
-  --state extend/github-projects/examples/goal-board-sync/state.yaml \
-  --dry-run \
-  --json
-```
-
-## Boundaries
-
-- `state.yaml` remains authoritative.
-- The sync is one-way from GoalBuddy to GitHub Projects.
-- Missing GitHub credentials block only live sync, not local dry-run validation.
-- Live sync creates or updates GitHub Project draft issues, fields, and the `Goal Board` view through the bundled script.
-- Agents must not fall back to Computer Use, browser automation, or the GitHub web UI for Project setup.
-- Agents must not claim ProjectV2 board views are UI-only; GitHub's REST Project views API supports creating board-layout views.
-- Native GitHub issue hierarchy and dependencies are represented as fields because ProjectV2 draft issues do not provide full issue relationship semantics.

package/goalbuddy/extend/github-projects/examples/goal-board-sync/state.yaml

@@ -1,63 +0,0 @@
-version: 2
-
-goal:
-  title: "Goal board sync MVP"
-  slug: "goal-board-sync-mvp"
-  kind: specific
-  tranche: "Mirror a GoalBuddy board into an external Kanban surface."
-  status: active
-
-rules:
-  pm_owns_state: true
-  one_active_task: true
-  max_write_workers: 1
-  no_implementation_without_worker_or_pm_task: true
-  no_completion_without_judge_or_pm_audit: true
-
-active_task: T002
-
-tasks:
-  - id: T001
-    type: scout
-    assignee: Scout
-    status: done
-    priority: P3
-    objective: "Map external board API requirements."
-    inputs:
-      - "Board API docs"
-    constraints:
-      - "Read-only."
-    expected_output:
-      - "Required scopes"
-      - "Field mapping"
-    receipt:
-      result: done
-      summary: "The board sync can read GoalBuddy state.yaml and mirror tasks into an external board."
-  - id: T002
-    type: worker
-    assignee: Worker
-    status: active
-    priority: P1
-    objective: "Implement one-way external board sync."
-    parent: T001
-    depends_on:
-      - T001
-    allowed_files:
-      - "extend/github-projects/scripts/**"
-      - "README.md"
-    verify:
-      - "node --test extend/github-projects/test/*.test.mjs"
-      - "node extend/github-projects/scripts/sync-github-project.mjs --state extend/github-projects/examples/goal-board-sync/state.yaml --dry-run"
-    stop_if:
-      - "Board API credentials are unavailable."
-    receipt: null
-  - id: T003
-    type: judge
-    assignee: Judge
-    status: queued
-    priority: P2
-    objective: "Audit whether the board sync MVP is ready to document."
-    parent: T002
-    depends_on:
-      - T002
-    receipt: null

package/goalbuddy/extend/github-projects/extension.yaml

@@ -1,43 +0,0 @@
-id: github-projects
-name: GitHub Projects
-kind: integration
-version: 0.1.1
-source_of_truth: local
-description: Mirror GoalBuddy state.yaml tasks into GitHub Projects with dry-run planning, ProjectV2 fields, draft issue upserts, and one Goal Board view.
-local_use_prompt: Run the bundled GitHub Projects sync script for docs/goals/<slug>/state.yaml. Use --dry-run first unless the user has approved live GitHub writes, then run the same script with GITHUB_TOKEN or GH_TOKEN and --project-id or --owner plus --project-number. Do not use Computer Use, browser automation, the GitHub web UI, or gh project as a fallback.
-use_when:
-  - A long-running GoalBuddy board needs stakeholder visibility in GitHub Projects.
-  - The team wants one-way sync from state.yaml into ProjectV2 draft issues.
-  - The PM needs a safe dry-run plan before using GitHub credentials.
-  - GoalBuddy receipts, verification commands, allowed files, owners, role/agent fields, credential gates, and dependencies should appear in a GitHub board.
-activation: publish_handoff
-outputs:
-  - GitHub Projects dry-run plan
-  - GitHub ProjectV2 draft issue sync
-  - Goal Board ProjectV2 view
-requires_approval: true
-safe_by_default: false
-reads:
-  - docs/goals/<slug>/state.yaml
-  - GITHUB_PROJECT_ID
-  - GITHUB_PROJECT_OWNER
-  - GITHUB_PROJECT_NUMBER
-writes:
-  - GitHub ProjectV2 draft issues
-  - GitHub ProjectV2 fields
-  - GitHub ProjectV2 Goal Board view
-side_effects:
-  - Live sync creates or updates GitHub Project draft issues, fields, and views.
-agent_instructions:
-  - Use the bundled sync script for all live GitHub Projects writes.
-  - Do not use Computer Use, browser automation, or the GitHub web UI to create or repair Project views.
-  - Do not replace the bundled script with gh project commands; the script uses GraphQL plus the REST Project views endpoint.
-  - Do not claim ProjectV2 board views are UI-only; the GitHub REST Project views API supports creating board-layout views.
-auth:
-  env:
-    - GITHUB_TOKEN
-supports:
-  dry_run: true
-  live_github_projects: true
-  credentials_required: true
-  one_way_sync: true