feat(agentos): add Hindsight long-term memory integration for AgentOS

[benfrank241]

Summary

Adds @vectorize-io/hindsight-agentos, a first-party integration giving AgentOS agents long-term memory via Hindsight. Resolves the maintainer request in framerslab/agentos#16.

AgentOS exposes a clean AgentMemoryProvider hook (getContext before generation, observe after) that auto-wires on every agent call path. This integration takes the lightweight external-wrapper route from the issue: createHindsightMemory(options) returns an AgentMemoryProvider backed by Hindsight — no fork of AgentOS internals required.

import { agent } from "@framers/agentos";
import { createHindsightMemory } from "@vectorize-io/hindsight-agentos";
import { Hindsight } from "@vectorize-io/hindsight-client";

const memory = createHindsightMemory({
  client: new Hindsight({ apiKey: process.env.HINDSIGHT_API_KEY }),
  bank: "ada",
  recall: { budget: "high", includeEntities: true },
  retain: { tags: ["source:agentos"] },
});

const ada = agent({ name: "Ada", memoryProvider: memory });

How it works

Hook	When	What it does
getContext	Before each model call	Recalls relevant memories from Hindsight, returns a context block AgentOS injects into the system prompt
observe	After each turn	Retains the user turn (and optionally the agent reply) so Hindsight extracts entities and consolidates into world/experience facts + mental models server-side

Both sides fail safe — a recall failure returns no context (the agent still responds) and retains are fire-and-forget by default so they never add turn latency. bank, all recall options (budget/types/maxTokens/includeEntities/labelTypes/heading) and retain options (async/tags/metadata/includeAgentMessages) are configurable; either side can be disabled.

Meets the "Adding New Integrations" checklist

• Tests — 18 vitest cases exercising the AgentMemoryProvider contract plus a harness that simulates AgentOS's own before/after turn wiring (recall injected into the prompt, both turns retained). The AgentMemoryProvider type is imported from the real @framers/agentos package.
• CI job — build-agentos-integration (npm ci → test → build), gated on detect-changes integrations-agentos, and registered in the PR-status report.
• Release — agentos added to VALID_INTEGRATIONS in scripts/release-integration.sh.
• Docs — gallery entry in integrations.json, integration page at docs-integrations/agentos.md, icon, and a row in the integrations README.

Test plan

• npm ci && npm test — 18/18 pass
• npm run build — ESM + DTS build clean (compiles against real @framers/agentos types)
• tsc --noEmit clean
• check-integrations.mjs / check-integration-seo.mjs — doc page + SEO pass
• check-integration-lockfiles.sh — lockfile resolves from npm registry
• test.yml YAML valid; release-integration.sh syntax OK