{
  "id": "lib-process:meta--github-copilot",
  "_kind": "LibraryProcess",
  "_file": "generated-library/processes.yaml",
  "_cluster": "generated-library",
  "attributes": {
    "displayName": "assimilation/harness/github-copilot",
    "description": "Orchestrate babysitter SDK integration into GitHub Copilot CLI agent.\n  GitHub CLI (`gh`) is GitHub's official CLI tool. It includes:\n  - `gh copilot` subcommand for AI features (suggest, explain)\n  - `gh copilot suggest` / `gh copilot explain` for one-shot AI interactions\n  - `gh extension` system for distributing custom CLI commands as repos\n  - GitHub Copilot in the CLI for agent-style coding (emerging feature)\n  The GitHub CLI is NOT a traditional coding harness like Claude Code or Codex.\n  It's a GitHub API client with Copilot features bolted on. The integration\n  approach differs from other harnesses:\n  - Hook system exists but limited: hooks.json with camelCase types\n    (sessionStart, sessionEnd, userPromptSubmitted, preToolUse, postToolUse,\n    errorOccurred) — but ONLY preToolUse can return flow-control decisions.\n    All other hook outputs are IGNORED. No stop-hook equivalent exists.\n  - Plugin system: manifest in .plugin/, .github/plugin/, .claude-plugin/,\n    or repo root. Install via `copilot plugin install OWNER/REPO`.\n  - Marketplace: marketplace.json, `copilot plugin marketplace add/browse/list`\n  - Plugin storage: ~/.copilot/installed-plugins/\n  - Skills: skills/NAME/SKILL.md format with frontmatter\n  - Extension model: `gh extension install owner/repo` (binary or script)\n  - Config: ~/.config/gh/ (hosts.yml, config.yml)\n  - Environment: GH_TOKEN, GITHUB_TOKEN, GH_HOST, GH_REPO, etc.\n  - GitHub Copilot Workspace and Copilot Agent may introduce richer surfaces\n  The research phase MUST verify the current state of:\n  - GitHub Copilot agent capabilities (beyond suggest/explain)\n  - Whether `gh copilot` supports agent loops, tool use, or MCP\n  - GitHub Copilot Workspace API/CLI if available\n  - Whether there's a session or conversation model\n  - Any hook or callback mechanism for continuation\n  This is a more speculative integration — the process must determine whether\n  GitHub Copilot CLI has evolved enough to support babysitter orchestration,\n  or if the integration should focus on the extension model as a distribution\n  mechanism with in-turn loop driving.",
    "libraryPath": "library/specializations/meta/assimilation/harness/github-copilot.js",
    "specialization": "meta"
  },
  "outgoingEdges": [
    {
      "from": "lib-process:meta--github-copilot",
      "to": "skill-area:ai-agent-development",
      "kind": "lib_requires_skill_area",
      "attributes": {
        "weight": 1
      }
    },
    {
      "from": "lib-process:meta--github-copilot",
      "to": "skill-area:orchestration-loop",
      "kind": "lib_requires_skill_area",
      "attributes": {
        "weight": 0.7
      }
    },
    {
      "from": "lib-process:meta--github-copilot",
      "to": "topic:developer-experience",
      "kind": "lib_covers_topic",
      "attributes": {
        "weight": 1
      }
    },
    {
      "from": "lib-process:meta--github-copilot",
      "to": "topic:integrations",
      "kind": "lib_covers_topic",
      "attributes": {
        "weight": 0.7
      }
    },
    {
      "from": "lib-process:meta--github-copilot",
      "to": "domain:software-engineering",
      "kind": "lib_applies_to_domain",
      "attributes": {
        "weight": 1
      }
    },
    {
      "from": "lib-process:meta--github-copilot",
      "to": "role:platform-engineer",
      "kind": "lib_involves_role",
      "attributes": {
        "weight": 1
      }
    },
    {
      "from": "lib-process:meta--github-copilot",
      "to": "specialization:meta",
      "kind": "lib_belongs_to_specialization",
      "attributes": {
        "weight": 0.9
      }
    }
  ],
  "incomingEdges": []
}