Skip to content

feat: MapCaseFile — key-value migration shim for casehub-poc compatibility #239

@mdproctor

Description

@mdproctor

Phase 3 migration item. casehub-poc's CaseFile is a string key → typed value map. casehub-engine's CaseContext is JSON-backed. This issue tracks a compatibility shim that eases migration for code written against the poc's key-value model.

Scope

  • MapCaseFileCaseContext implementation backed by Map<String, Object>
  • Serialises the map to JSON for engine consumption
  • Provides get(key), put(key, value), contains(key) API matching the poc's CaseFile interface
  • Intended as a migration stepping stone, not a long-term API

Refs casehub-poc migration plan (Phase 3): docs/superpowers/specs/2026-04-14-casehub-engine-migration-plan.md

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestmigrationCapability existing in casehub-poc, or planned in its design/architecture docs

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions