Skip to content

Normalize OpenLoops storage-kit snapshot#84

Open
andrei-hasna wants to merge 2 commits into
mainfrom
openloops/open-loops/2b166a36-1e7c-4882-be7f-610c4f478d39-a3f53908
Open

Normalize OpenLoops storage-kit snapshot#84
andrei-hasna wants to merge 2 commits into
mainfrom
openloops/open-loops/2b166a36-1e7c-4882-be7f-610c4f478d39-a3f53908

Conversation

@andrei-hasna

Copy link
Copy Markdown
Contributor

Summary

  • Normalize OpenLoops generated storage-kit to machine-level @hasna/contracts vendor-kit 0.5.1 output.
  • Carry docs/SHARED_KIT_EXTRACTION_INVENTORY.md from completed dependency task 8fd378e0.
  • Remove invalid package metadata drift from the existing branch so package.json and bun.lock do not change versus main.

Validation

  • git diff --check
  • git diff --cached --check
  • contracts vendor-kit --check (contracts 0.5.1)
  • bun run typecheck
  • bun run test:boundary
  • bun test src/lib/storage/postgres.test.ts src/lib/storage/postgres-loop-storage.test.ts src/lib/storage/postgres-concurrency.test.ts (8 pass, 16 skip live Postgres)
  • staged credential-pattern scan

Notes

  • bunx @hasna/contracts resolves to installed published @hasna/contracts 0.4.1 after install and fails against the vendored 0.5.1 kit. npm registry currently lists @hasna/contracts versions through 0.4.2, while the machine-level contracts CLI is 0.5.1.
  • No package publish, Bun release-age exclusion edit, or sibling consumer migration is included.

Task: 2b166a36-1e7c-4882-be7f-610c4f478d39

- Regenerate vendored storage-kit (0.4.0 -> 0.5.1) so the CLI/MCP cloud
  transport matches the deployed serve 0.4.17 contract.
- Bump @hasna/loops 0.4.17 -> 0.4.18.
- Move @hasna/contracts to optionalDependencies (^0.5.1): the client
  (cli/mcp/daemon/runner) has zero runtime imports of contracts — only
  serve uses @hasna/contracts/auth — so a client tarball install must not
  hard-require an unpublished registry version.

Client routes reads+writes to https://loops.hasna.xyz/v1 when
HASNA_LOOPS_API_URL + HASNA_LOOPS_API_KEY are set (verified live).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant