CS-10671: Rename Ticket → Issue, trim unused fields, add Phase 2 deps

.github/workflows/ci-software-factory.yaml

@@ -0,0 +1,80 @@
+name: CI Software Factory
+
+on:
+  push:
+    branches:
+      - main
+      - ci-bisect
+      - ci-bisect-**
+  pull_request:
+    paths:
+      - ".github/workflows/ci-software-factory.yaml"
+      - "packages/runtime-common/**"
+      - "packages/base/**"
+      - "packages/boxel-icons/**"
+      - "packages/host/**"
+      - "packages/matrix/**"
+      - "packages/postgres/**"
+      - "packages/realm-server/**"
+      - "packages/software-factory/**"
+      - "package.json"
+      - "pnpm-lock.yaml"
+  workflow_dispatch:
+
+concurrency:
+  group: ci-software-factory-${{ github.head_ref || github.run_id }}
+  cancel-in-progress: true
+
+permissions:
+  checks: write
+  contents: read
+  id-token: write
+  pull-requests: write
+
+jobs:
+  test-web-assets:
+    name: Build test web assets
+    uses: ./.github/workflows/test-web-assets.yaml
+
+  software-factory-test:
+    name: Software Factory Tests
+    needs: test-web-assets
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
+      - uses: ./.github/actions/init
+      - name: Download test web assets
+        uses: actions/download-artifact@b14cf4c92620c250e1c074ab0a5800e37df86765 # 4.2.0
+        with:
+          name: ${{ needs.test-web-assets.outputs.artifact_name }}
+          path: .test-web-assets-artifact
+      - name: Restore test web assets into workspace
+        shell: bash
+        run: |
+          shopt -s dotglob
+          cp -a .test-web-assets-artifact/. ./
+      - name: Install Playwright Browsers
+        run: pnpm exec playwright install
+        working-directory: packages/software-factory
+      - name: Run Node tests
+        run: pnpm test:node
+        working-directory: packages/software-factory
+      - name: Serve test assets (icons + host dist)
+        uses: JarvusInnovations/background-action@2428e7b970a846423095c79d43f759abf979a635 # 1.0.7
+        with:
+          run: mise run ci:serve-test-assets &
+          wait-for: 3m
+          wait-on: |
+            http-get://localhost:4200
+            http-get://localhost:4206
+      - name: Run Playwright tests
+        run: pnpm test:playwright
+        working-directory: packages/software-factory
+      - name: Upload Playwright traces
+        if: ${{ !cancelled() }}
+        uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # 4.6.1
+        with:
+          name: software-factory-playwright-traces
+          path: packages/software-factory/test-results/**/trace.zip
+          retention-days: 30
+          if-no-files-found: ignore

.github/workflows/ci.yaml

@@ -30,7 +30,6 @@ jobs:
       boxel-ui: ${{ steps.filter.outputs.boxel-ui }}
       matrix: ${{ steps.filter.outputs.matrix }}
       realm-server: ${{ steps.filter.outputs.realm-server }}
-      software-factory: ${{ steps.filter.outputs.software-factory }}
       vscode-boxel-tools: ${{ steps.filter.outputs.vscode-boxel-tools }}
       workspace-sync-cli: ${{ steps.filter.outputs.workspace-sync-cli }}
       boxel-cli: ${{ steps.filter.outputs.boxel-cli }}
@@ -102,15 +101,6 @@ jobs:
               - 'packages/eslint-plugin-boxel/**'
               - 'packages/postgres/**'
               - 'packages/realm-server/**'
-            software-factory:
-              - *shared
-              - 'packages/base/**'
-              - 'packages/boxel-icons/**'
-              - 'packages/host/**'
-              - 'packages/matrix/**'
-              - 'packages/postgres/**'
-              - 'packages/realm-server/**'
-              - 'packages/software-factory/**'
             vscode-boxel-tools:
               - *shared
               - 'packages/vscode-boxel-tools/**'
@@ -129,7 +119,7 @@ jobs:
   test-web-assets:
     name: Build test web assets
     needs: change-check
-    if: needs.change-check.outputs.boxel == 'true' || needs.change-check.outputs.boxel-ui == 'true' || needs.change-check.outputs.matrix == 'true' || needs.change-check.outputs.realm-server == 'true' || needs.change-check.outputs.software-factory == 'true' || needs.change-check.outputs.vscode-boxel-tools == 'true' || needs.change-check.outputs.workspace-sync-cli == 'true' || github.ref == 'refs/heads/main' || needs.change-check.outputs.run_all == 'true'
+    if: needs.change-check.outputs.boxel == 'true' || needs.change-check.outputs.boxel-ui == 'true' || needs.change-check.outputs.matrix == 'true' || needs.change-check.outputs.realm-server == 'true' || needs.change-check.outputs.vscode-boxel-tools == 'true' || needs.change-check.outputs.workspace-sync-cli == 'true' || github.ref == 'refs/heads/main' || needs.change-check.outputs.run_all == 'true'
     uses: ./.github/workflows/test-web-assets.yaml
     concurrency:
       group: ci-test-web-assets-${{ github.head_ref || github.run_id }}
@@ -678,53 +668,6 @@ jobs:
           junit_files: realm-server.xml
           check_name: Realm Server Test Results
 
-  software-factory-test:
-    name: Software Factory Tests
-    needs: [change-check, test-web-assets]
-    if: needs.change-check.outputs.software-factory == 'true' || github.ref == 'refs/heads/main' || needs.change-check.outputs.run_all == 'true'
-    runs-on: ubuntu-latest
-    concurrency:
-      group: software-factory-test-${{ github.head_ref || github.run_id }}
-      cancel-in-progress: true
-    steps:
-      - uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
-      - uses: ./.github/actions/init
-      - name: Download test web assets
-        uses: actions/download-artifact@b14cf4c92620c250e1c074ab0a5800e37df86765 # 4.2.0
-        with:
-          name: ${{ needs.test-web-assets.outputs.artifact_name }}
-          path: .test-web-assets-artifact
-      - name: Restore test web assets into workspace
-        shell: bash
-        run: |
-          shopt -s dotglob
-          cp -a .test-web-assets-artifact/. ./
-      - name: Install Playwright Browsers
-        run: pnpm exec playwright install
-        working-directory: packages/software-factory
-      - name: Run Node tests
-        run: pnpm test:node
-        working-directory: packages/software-factory
-      - name: Serve test assets (icons + host dist)
-        uses: JarvusInnovations/background-action@2428e7b970a846423095c79d43f759abf979a635 # 1.0.7
-        with:
-          run: mise run ci:serve-test-assets &
-          wait-for: 3m
-          wait-on: |
-            http-get://localhost:4200
-            http-get://localhost:4206
-      - name: Run Playwright tests
-        run: pnpm test:playwright
-        working-directory: packages/software-factory
-      - name: Upload Playwright traces
-        if: ${{ !cancelled() }}
-        uses: actions/upload-artifact@4cec3d8aa04e39d1a68397de0c4cd6fb9dce8ec1 # 4.6.1
-        with:
-          name: software-factory-playwright-traces
-          path: packages/software-factory/test-results/**/trace.zip
-          retention-days: 30
-          if-no-files-found: ignore
-
   vscode-boxel-tools-package:
     name: Boxel Tools VS Code Extension package
     needs: [change-check, test-web-assets]

packages/software-factory/.agents/skills/boxel-development/references/dev-qunit-testing.md

@@ -141,5 +141,5 @@ When tests fail, the orchestrator feeds test failure details back to the agent.
 - **All test data lives in browser memory only** — never write to external realms during tests.
 - **Use `import.meta.url`** to resolve card definitions — never hardcode realm URLs.
 - **Use `data-test-*` attributes** for stable test selectors, not CSS classes.
-- **Every ticket must have at least one test file** as `{card-name}.test.gts` co-located with the card definition.
+- **Every issue must have at least one test file** as `{card-name}.test.gts` co-located with the card definition.
 - **Test files live in the target realm** as realm files alongside the card definitions they test.

packages/software-factory/.agents/skills/boxel-development/references/dev-realm-search.md

@@ -40,9 +40,9 @@ Use `eq` to match exact field values. You must specify `on` to scope the field t
   "filter": {
     "on": {
       "module": "http://localhost:4201/software-factory/darkfactory",
-      "name": "Ticket"
+      "name": "Issue"
     },
-    "eq": { "ticketStatus": "in_progress" }
+    "eq": { "status": "in_progress" }
   }
 }
 ```
@@ -226,21 +226,21 @@ You can only filter/sort on fields that exist on the card type. To find which fi
   "commandInput": {
     "codeRef": {
       "module": "http://localhost:4201/software-factory/darkfactory",
-      "name": "Ticket"
+      "name": "Issue"
     }
   }
 }
 ```
 
-2. The result contains `attributes.properties` listing all searchable fields (e.g., `ticketStatus`, `summary`, `priority`).
+2. The result contains `attributes.properties` listing all searchable fields (e.g., `status`, `summary`, `priority`).
 
 3. Use those field names in your `eq`, `contains`, `range`, or `sort` with the matching `on` type.
 
-The card tools (`update_project`, `update_ticket`, `create_knowledge`, `create_catalog_spec`) also have dynamic JSON schemas in their parameters that list available fields.
+The card tools (`update_project`, `update_issue`, `create_knowledge`, `create_catalog_spec`) also have dynamic JSON schemas in their parameters that list available fields.
 
 ### Inheritance
 
-Filtering on a base card type's fields matches all cards that inherit from it. For example, filtering on `CardDef` fields like `cardTitle` or `cardDescription` finds cards of any type. Filtering on a `Ticket` field like `ticketStatus` finds only Ticket cards (and any subtypes of Ticket).
+Filtering on a base card type's fields matches all cards that inherit from it. For example, filtering on `CardDef` fields like `cardTitle` or `cardDescription` finds cards of any type. Filtering on an `Issue` field like `status` finds only Issue cards (and any subtypes of Issue).
 
 ### Searching Through Relationship Fields
 

packages/software-factory/.agents/skills/software-factory-operations/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: software-factory-operations
-description: Use when implementing cards in a target realm through the factory execution loop — covers the tool-use workflow for searching, writing, testing, and updating tickets via factory tools.
+description: Use when implementing cards in a target realm through the factory execution loop — covers the tool-use workflow for searching, writing, testing, and updating issues via factory tools.
 ---
 
 # Software Factory Operations
@@ -12,7 +12,7 @@ Use this skill when operating inside the factory execution loop. The factory age
 - **Source realm** (`packages/software-factory/realm`)
   Publishes shared modules, briefs, templates, and tracker schema. Never write to this realm.
 - **Target realm** (user-specified, passed to `factory:go`)
-  Receives all generated artifacts: Project, Ticket, KnowledgeArticle, card definitions, card instances, Catalog Spec cards, and QUnit test files.
+  Receives all generated artifacts: Project, Issue, KnowledgeArticle, card definitions, card instances, Catalog Spec cards, and QUnit test files.
 
 ## Available Tools
 
@@ -30,7 +30,7 @@ The agent has these tools during the execution loop. Use them by name — they a
 ### Updating Project State
 
 - `update_project({ path, attributes, relationships? })` — Update a Project card in the target realm. The tool's parameters include a dynamic JSON schema describing available fields — use it to know valid field names and types. The tool auto-constructs the JSON:API document with the correct `adoptsFrom`.
-- `update_ticket({ path, attributes, relationships? })` — Update a Ticket card. Same structured interface with dynamic field schema in the tool parameters.
+- `update_issue({ path, attributes, relationships? })` — Update an Issue card. Same structured interface with dynamic field schema in the tool parameters.
 - `create_knowledge({ path, attributes, relationships? })` — Create or update a KnowledgeArticle card. Same structured interface with dynamic field schema in the tool parameters.
 - `create_catalog_spec({ path, attributes, relationships? })` — Create a Catalog Spec card in the target realm's `Spec/` folder. Makes a card definition discoverable in the Boxel catalog. Same structured interface with dynamic field schema. The tool auto-constructs the document with `adoptsFrom` pointing to `https://cardstack.com/base/spec#Spec`.
 
@@ -60,20 +60,20 @@ Returns `{ status: "ready", result: "<serialized JsonCard with schema>" }`. Pars
 
 ### Control Flow
 
-- `signal_done()` — Signal that the current ticket is complete. Call this only after all implementation and test files have been written.
+- `signal_done()` — Signal that the current issue is complete. Call this only after all implementation and test files have been written.
 - `request_clarification({ message })` — Signal that you cannot proceed and need human input. Describe what is blocking.
 
 ## Required Flow
 
 1. **Inspect before writing.** Use `search_realm` and `read_file` to understand what already exists in the target realm before creating or modifying files.
-2. **Move ticket to `in_progress`.** Use `update_ticket` to set the ticket status before starting implementation.
+2. **Move issue to `in_progress`.** Use `update_issue` to set the issue status before starting implementation.
 3. **Write card definitions** (`.gts`) via `write_file` to the target realm.
 4. **Write card instances** (`.json`) via `write_file` to the target realm.
 5. **Write a Catalog Spec card** (`Spec/<card-name>.json`) for each top-level card defined in the brief. Link sample instances via `linkedExamples`.
-6. **Write `.test.gts` test files** co-located with card definitions via `write_file` to the target realm. Every ticket must have at least one test file.
+6. **Write `.test.gts` test files** co-located with card definitions via `write_file` to the target realm. Every issue must have at least one test file.
 7. **Call `signal_done()`** when all implementation and test files are written. The orchestrator triggers test execution after this.
 8. **If tests fail**, the orchestrator feeds failure details back. Use `read_file` to inspect current state, then `write_file` to fix implementation or test files. Call `signal_done()` again.
-9. **Update ticket state** via `update_ticket` — update notes, acceptance criteria, and related knowledge as work progresses.
+9. **Update issue state** via `update_issue` — update notes, acceptance criteria, and related knowledge as work progresses.
 
 ## Target Realm Artifact Structure
 
@@ -86,11 +86,11 @@ target-realm/
 ├── Spec/
 │   └── card-name.json               # Catalog Spec card
 ├── Test Runs/
-│   └── ticket-slug-1.json           # TestRun card
+│   └── issue-slug-1.json            # TestRun card
 ├── Projects/
 │   └── project-name.json            # Project card
-├── Tickets/
-│   └── ticket-slug.json             # Ticket card
+├── Issues/
+│   └── issue-slug.json              # Issue card
 └── Knowledge Articles/
     └── article-name.json            # KnowledgeArticle card
 ```

packages/software-factory/README.md

@@ -7,15 +7,15 @@ The software factory is an automated card-development system that takes a brief
 The factory flow has four phases:
 
 1. **Intake** — Fetch a brief card from a source realm, normalize it into a structured representation
-2. **Bootstrap** — Create a target realm (if needed), populate it with a Project card, Knowledge Articles, and starter Tickets
-3. **Implementation** — An LLM agent picks up the active ticket and uses tool calls to write card definitions (`.gts`), sample instances (`.json`), catalog specs (`Spec/`), and QUnit test files (`.test.gts`) into the target realm
+2. **Bootstrap** — Create a target realm (if needed), populate it with a Project card, Knowledge Articles, and starter Issues
+3. **Implementation** — An LLM agent picks up the active issue and uses tool calls to write card definitions (`.gts`), sample instances (`.json`), catalog specs (`Spec/`), and QUnit test files (`.test.gts`) into the target realm
 4. **Verification** — The orchestrator runs QUnit tests via Playwright in a real browser, collects structured results into a TestRun card, and feeds failures back to the agent for iteration
 
-The agent iterates (implement → test → fix) until tests pass or max iterations are reached. The orchestrator (the "ralph loop") controls iteration count, test execution, and ticket selection deterministically — the LLM handles only the implementation work.
+The agent iterates (implement → test → fix) until tests pass or max iterations are reached. The orchestrator (the "ralph loop") controls iteration count, test execution, and issue selection deterministically — the LLM handles only the implementation work.
 
 ### Realm Roles
 
-- **Source realm** (`packages/software-factory/realm/`) — publishes shared modules, card type definitions (Project, Ticket, KnowledgeArticle, TestRun), briefs, and templates. Never written to by the factory.
+- **Source realm** (`packages/software-factory/realm/`) — publishes shared modules, card type definitions (Project, Issue, KnowledgeArticle, TestRun), briefs, and templates. Never written to by the factory.
 - **Target realm** (user-specified) — receives all generated artifacts: card definitions, instances, specs, test files, and TestRun results.
 - **Fixture realm** (`test-fixtures/`) — disposable test input for development-time verification of the factory itself.
 
@@ -24,7 +24,7 @@ The agent iterates (implement → test → fix) until tests pass or max iteratio
 | Path                  | What it is                                                          |
 | --------------------- | ------------------------------------------------------------------- |
 | `Projects/`           | Project card with objective, scope, success criteria                |
-| `Tickets/`            | Ticket cards tracking implementation work                           |
+| `Issues/`             | Issue cards tracking implementation work                            |
 | `Knowledge Articles/` | Context articles derived from the brief                             |
 | `*.gts`               | Card definition files                                               |
 | `*.test.gts`          | Co-located QUnit test files                                         |
@@ -81,7 +81,7 @@ The `--debug` flag shows LLM prompts, tool calls and their results, and `console
 | Folder / File              | What it is                                                                |
 | -------------------------- | ------------------------------------------------------------------------- |
 | `Projects/`                | A Project card with the brief's objective and success criteria            |
-| `Tickets/`                 | Ticket cards — the active ticket should show status `done`                |
+| `Issues/`                  | Issue cards — the active issue should show status `done`                  |
 | `Knowledge Articles/`      | Context articles derived from the brief                                   |
 | `*.gts`                    | Card definition file(s) for the implemented card                          |
 | `*.test.gts`               | Co-located QUnit test file(s)                                             |