Add issue tracker cards and project-backed kanban board to software-factory

[burieberry]

• Introduce generic kanbanBoard card and no-frills version of issue-tracker, currently in software-factory
• Added sample cards in experiments-realm for demo

Summary

• split up card definitions for issue tracker and related cards: issue, comment, knowledge article, agent-profile
• add generic kanban-board card with customizable columns and polymorphic cards
• extend kanban-board for IssueTrackerBoard with columns and enum options related to issue-tracker statuses
• use the new boxel-ui drag-and-drop kanban board in the project-backed issue tracker board
• update the software-factory realm wiring and dependencies to expose the new issue tracker experience
• add board creation into software-factory operations and tests
• test coverage and updates

Next Steps:

• Move issue-tracker out of software-factory
• More test coverage on functionality
• UI polish

[github-actions]

Host Test Results

    1 files  ±0      1 suites  ±0   1h 42m 29s ⏱️ - 3m 24s
2 565 tests ±0  2 550 ✅ +11  15 💤 ±0  0 ❌ ± 0 
2 584 runs  ±0  2 569 ✅ +22  15 💤 ±0  0 ❌  - 11 

Results for commit 9f09e9e. ± Comparison against earlier commit d0d9fd9.

Realm Server Test Results

    1 files  ±0      1 suites  ±0   15m 27s ⏱️ - 2m 7s
1 248 tests +9  1 248 ✅ +9  0 💤 ±0  0 ❌ ±0 
1 326 runs  +9  1 326 ✅ +9  0 💤 ±0  0 ❌ ±0 

Results for commit 9f09e9e. ± Comparison against earlier commit d0d9fd9.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d49d7990eb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[lukemelia]

Do we want test coverage for this?

[burieberry]

Do we want test coverage for this?

Updated software-factory operations and tests to include board creation. Component itself has tests in boxel-ui. More card tests can be added when cards are moved out of software-factory.

[habdelra]

Probably a better test would be to use a playwright spec test in the software factory to test the actual rendering of the new card defs, test moving the issues between column sin the kanban board, adding comments asserting the comments appear in the issue, etc. like full integration tests via the DOM. the node tests are mostly cheating in this regard because they would rely on mocks of the realm server and don't actually try to render the card.

[burieberry]

Probably a better test would be to use a playwright spec test in the software factory to test the actual rendering of the new card defs, test moving the issues between column sin the kanban board, adding comments asserting the comments appear in the issue, etc. like full integration tests via the DOM. the node tests are mostly cheating in this regard because they would rely on mocks of the realm server and don't actually try to render the card.

Yes, I want to add ui tests after moving it out of software-factory because it's been a huge struggle to be able to write them as playwright tests. Other option is I move them out now. The kanban component itself has tests in boxel-ui.

[habdelra]

Probably a better test would be to use a playwright spec test in the software factory to test the actual rendering of the new card defs, test moving the issues between column sin the kanban board, adding comments asserting the comments appear in the issue, etc. like full integration tests via the DOM. the node tests are mostly cheating in this regard because they would rely on mocks of the realm server and don't actually try to render the card.

Yes, I want to add ui tests after moving it out of software-factory because it's been a huge struggle to be able to write them as playwright tests. Other option is I move them out now. The kanban component itself has tests in boxel-ui.

sounds good--i trust your judgement