Migrating from @hellmai/lumenflow-core
LumenFlow v7 removes @hellmai/lumenflow-core. The package was a temporary compatibility layer whose
implementations moved to their real owners during the kernel/pack boundary migration. Its root and
subpath imports no longer resolve.
Ownership map
Section titled “Ownership map”| Concern | Canonical owner |
|---|---|
| Kernel contracts, policy, scope, and evidence | @hellmai/lumenflow-kernel |
| Generic Node.js adapters and workspace primitives | @hellmai/lumenflow-host |
| Generic runtime coordination contracts | @hellmai/lumenflow-runtime |
| WU lifecycle, gates, lanes, planning, recovery, and completion | @hellmai/lumenflow-packs-software-delivery |
| Workflow configuration and schemas | @hellmai/lumenflow-packs-software-delivery/config |
| Initiatives, delivery metrics, and workflow memory | the matching Software Delivery Pack subpath |
Examples
Section titled “Examples”When a symbol is not listed in the public export map of an owning package, treat it as internal. Prefer the supported CLI command for lifecycle operations rather than importing command internals.
Verification
Section titled “Verification”From the consumer repository:
The search should return no active dependency, import, export, mock, or runtime-loader edge. A historical changelog entry may retain the old package name when it is clearly labelled as history.
Timeline
Section titled “Timeline”| Release | Status |
|---|---|
| v5.8.11 | Selected subpaths deprecated. |
| v6 | Implementations moved to canonical owners; compatibility forwarders remained. |
| v7 | Compatibility package and every subpath removed. |
ADR-012 in the source repository records the enforced dependency direction. See Package Architecture for the current package graph.