boost: set up initial test infrastructure

[durandom]

Problem

The boost workspace has no test infrastructure yet. Other workspaces (scorecard, lightspeed, orchestrator) all use backstage-cli repo test with Jest.

Expected behavior

• A basic test setup that allows yarn test to run from workspaces/boost/
• At minimum, a placeholder test file that proves the test runner works
• Follow patterns from other workspaces in this monorepo (e.g., scorecard, lightspeed)

Acceptance criteria

1. yarn test runs and passes in workspaces/boost/
2. yarn openspec:validate passes
3. At least one test file exists in a plugin or package directory

[fullsend-ai-triage]

🤖 Triage · Started 9:32 AM UTC
Commit: 2a53627 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Category: Feature (new test infrastructure) · Severity: Low

Problem

The boost workspace currently has no plugins/ or packages/ directories and no test files. While package.json defines a test script (backstage-cli repo test), there are no test targets for it to run.

Recommended Approach

Follow the pattern established by the scorecard workspace:

1. Create a plugins/ directory with at least one plugin or package containing a test file
2. Add a placeholder test to prove the Jest runner works via backstage-cli repo test
3. Verify both yarn test and yarn openspec:validate pass

Note: the scorecard workspace uses NODE_OPTIONS='--experimental-vm-modules' in its test script — evaluate whether boost needs the same.

Proposed Verification

cd workspaces/boost/
yarn test        # should exit 0 with at least 1 test suite passing
yarn openspec:validate  # should pass

This is a good candidate for a first contribution to the boost workspace, as the acceptance criteria are well-defined and the pattern is established in other workspaces.

---

Labels: Adding enhancement and good first issue labels — this is a straightforward infrastructure setup task with clear prior art in other workspaces.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 9:32 AM UTC · Completed 9:35 AM UTC
Commit: 2a53627 · View workflow run →

[durandom]

/fs-code

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 3:23 PM UTC · Completed 4:00 PM UTC
Commit: 0b54852 · View workflow run →

[durandom]

/fs-code

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 2:31 PM UTC · Completed 2:34 PM UTC
Commit: 5a4ac55 · View workflow run →

[fullsend-ai-coder]

An open PR already addresses this issue — skipping automated implementation.

• feat(boost): set up initial test infrastructure with boost-common plugin #3343 by @app/fullsend-ai-coder

To override, comment /fs-code --force on this issue.

_{Posted by fullsend pre-code check}