specflow init --from-features fails: table features has no column named problem_type

[mellanon]

Bug

specflow init --from-features features.json fails with:

SQLiteError: table features has no column named problem_type

Steps to Reproduce

1. Run the specflow interview to generate features.json
2. Run specflow init --from-features features.json "description"
3. Error occurs on insert — the features table schema doesn't include a problem_type column, but the --from-features code path tries to insert one

Expected

specflow init --from-features should either:

• Include problem_type in the DB schema, or
• Not attempt to insert problem_type if the column doesn't exist

Environment

• specflow-bundle (latest main)
• Reproduced in pai-collab-bundle project

Additional Context

--force flag doesn't help — same error. Deleting the DB and re-running specflow migrate also fails since there's no existing DB to migrate.

[mellanon]

Root Cause Found

The issue is not a missing schema definition — problem_type is correctly defined in the migrations. The problem is that migrations never run when using the compiled binary.

Why

In src/lib/database.ts, the migrations directory is resolved via:

join(import.meta.dir, "..", "..", "migrations")

This works when running from source (bun src/index.ts), resolving to:

packages/specflow/migrations/

But specflow is installed as a compiled Bun binary (bun build --compile). In a compiled binary, import.meta.dir resolves to the binary's location (~/bin/), so the migrations path becomes something like ~/migrations/ — which doesn't exist. The migration runner silently finds no migrations, the problem_type column is never added, and the insert fails.

Verification

Running from source works:

bun packages/specflow/src/index.ts init --from-features features.json "description"
# succeeds (after clearing existing DB)

Running the compiled binary fails:

specflow init --from-features features.json "description"
# SQLiteError: table features has no column named problem_type

Suggested Fix

Embed migrations at compile time, or resolve the migrations path relative to a known anchor (e.g., bundled as string literals, or using __dirname with a fallback).