14 Commits

Author	SHA1	Message	Date
Nicolò Boschi	6f2799569f	docs: make every integration changelog reachable, and compact the Integrations Hub (#4005) ... * docs: link every integration changelog from its doc page The release script has written a changelog page per integration since 0.4.20 (src/pages/changelog/integrations/<slug>.md), but nothing reliably linked them: 16 of 61 doc pages carried a "View Changelog" link, and the only index was a hand-written table at the bottom of /changelog listing 6 of the 48 pages, stale since the release that introduced them. coding-agents was one of the 31 pages with a changelog nobody could reach except by guessing the URL. Adds the link to the 30 pages missing one, plus a third invariant in check-integrations.mjs so the next one can't ship unlinked: every changelog page whose integration has a gallery entry must be linked from its doc page. coding-agents.md is generated, so its link goes in the README as an absolute hindsight.vectorize.io URL — the sync script rewrites our own absolute URLs to site-relative, so it resolves on npm, GitHub and the docs site. It sits outside the skill:begin regions, so SKILL.md is unchanged. Claude-Session: https://claude.ai/code/session_01DNWFQn8AUN6SApcswHG3aN * docs(integrations): compact grouped gallery with Docs/Changelog buttons The Integrations Hub listed 60 three-line cards with a repeated "Hindsight Team" byline and an OFFICIAL badge on 52 of them, running 6092px tall — scanning it meant scrolling past what you came for. Cards are now a compact row (icon, name, two-line description) grouped by category, with the featured three using the same row tinted rather than a second card design: 4352px, and the shape of the catalogue is visible at a glance. Each card carries Docs and Changelog buttons. Which integrations have a changelog comes from a new build-time plugin that indexes src/pages/changelog/integrations/*.md and joins integrations.json on the link slug (vercel-ai-sdk -> /sdks/integrations/ai-sdk -> ai-sdk.md), so an integration grows the button on its first release with nothing to update by hand. The card is a <div> now — nested anchors are invalid — so the name and the pills are the links, not the whole card. /changelog's first line points here instead of carrying its own listing. Also drops the 14 CSS classes the old card owned, and shares CATEGORY_LABELS / groupByCategory from src/lib/integrations.ts so the taxonomy has one definition. Claude-Session: https://claude.ai/code/session_01DNWFQn8AUN6SApcswHG3aN	2026-09-02 10:21:08 +02:00
Nicolò Boschi	1b74e3efa8	docs(coding-agents): generate the companion skill from the README (#3735) (#3753) ... The skill and the README documented the same configuration in two hand- maintained files, and they drifted in both directions. The skill never named `bankIdTemplate`, `dynamicBankId`, `optInOnly`, `optInPaths`, `retainTags`, `retainMetadata`, `resolveWorktrees`, `maxParallelRetains` or any daemon setting, and it stated outright that the package reads "no environment variables" — there are 35 (core/config.ts ENV_KEYS). That is the half #3735 reported. The README had lost the other half: `autoReflect` and `surveyRefreshCommits` were documented only in the skill, and neither file mentioned that `HINDSIGHT_CONFIG` relocates the config file, that the layering chain ends at `banks.<resolvedBankId>`, or that `optInPaths` takes a comma-separated env value like its sibling `retainTags`. The README is now the single source. scripts/build-skill.mjs copies the regions it marks with `skill:begin` / `skill:end` into skill/SKILL.md, normalising heading levels per region; only the agent-facing half — which tools to call, crediting memory, correcting a stale memory — stays separate, in skill-src/preamble.md. The docs page was already generated from the README; its generator now strips the markers, which MDX cannot parse. The skill's operative debugging knowledge (sync-status readiness, resetting a bank, the survey-baseline/gitlog marker documents, the session_start/deepen_started triage rule) moved into the README, so it reaches users and the docs site too. src/docs-freshness.test.ts fails when the skill is stale, when a field of `RawConfig` is readable from a config file but named nowhere in the README — the check that makes this class of drift impossible to reintroduce — and when a documented claim about the env layer stops holding (every key really is `HINDSIGHT_<FIELD_IN_CAPS>`; the four map-valued settings really are file-only). It also unit-tests the marker parser. prepublishOnly regenerates the skill so a publish cannot ship a stale copy.	2026-08-24 11:06:28 +02:00
Nicolò Boschi	8b78b4ac04	test: assert memory state via the engine read API, not raw SQL (#3591) ... The suite asserted memory state by querying `memory_units` / `memory_links` / `unit_entities` directly. That couples tests to the physical schema and makes them unable to run against any store that keeps memory rows outside Postgres. This ports what the read API can answer, extends it where it could not, and marks the residue that is Postgres-shaped by nature. **Ported to the engine API.** The "unconsolidated count" assertions spelled out `consolidated_at IS NULL AND consolidation_failed_at IS NULL AND fact_type IN ('experience','world')` — character-for-character what `list_memory_units(consolidation_state='pending')` already means, so seven sites across five files became one call. Observation lineage, entity/tag checks and chunk provenance moved to `list_memory_units` / `get_memory_unit` / `list_document_chunks`; where the old query was an inner join, the port keeps the same filtering and says why. **Read model extended** so the rest could follow: `updated_at` and `source_memory_ids` on list items, `entity_kind` on entity items, and a list-valued `fact_type` that matches any of them. Every field is a column of the row the query already fetched — the projection grows, the plan does not — so no opt-in flag was needed and production paths pay nothing. Covered by a new test module driving it all through the engine on retain-written units. **260 of 6297 tests marked `memory_backend_incompatible`**, in two passes: those that assert Postgres-internal state (raw `memory_links` counts, `embedding` / `search_vector`), and those whose fixtures only exist in Postgres. The second set was chosen on evidence — each both failed against a non-SQL store and touches those tables in its body, a helper, or a fixture — never by grep alone. Postgres runs are unchanged; the marker only takes effect behind `-m 'not memory_backend_incompatible'`. Also green-lights two checks that were red before this branch: the repo formatter over five test files, and the coding-agents docs generator, which now rewrites our own doc links to site-relative the way it already did for assets — the naive regeneration would have degraded the docs-skill reference's file-relative links.	2026-08-19 00:23:44 +02:00
Nicolò Boschi	fecacc4ea8	docs: launch Coding Agents + mark the per-agent plugins superseded (#3162) ... * docs: launch the Coding Agents page and mark the per-agent plugins superseded Hold until the Coding Agents plugin is announced — merging this makes the page public and tells existing users their plugin is legacy, so it should land with the announcement rather than before it. Two halves: - Launch. Undoes the deliberate hide: the page drops `unlisted`, its entry returns to integrations.json (which drives both the gallery and the sidebar), and coding-agents leaves the EXCLUDED set in check-integrations.mjs, so the released-tag check guards it like every other integration. - Supersede. The six overlapping integrations — claude-code, codex, opencode, cursor-cli, cline, copilot-cli — get an admonition in the style already used on the Hermes page: what replaces them, the install command for their harness, and a link to the migration section. Pages and packages keep working; nothing is deleted and no registry deprecation is published, so existing links and installs are unaffected. Each notice states plainly that memory does not move — the old plugins scope a bank per agent per project where this one uses a bank per repo — and points at `--import-conversations` for Claude Code and Codex, the two whose transcripts record enough to attribute a session to a repo. The other four say so instead of implying an import exists. * docs: group the integrations sidebars into coding agents / frameworks / apps Both sidebars driven by integrations.json rendered one flat run of 59 entries. Split them into three groups so a coding agent is distinguishable from an SDK. The existing `category` field couldn't drive this on its own: its `tool` bucket mixed CLI agents and editors with chat apps, note-taking and voice platforms. The 19 coding agents move to a new `coding-agent` category; `framework` is unchanged, and `tool`/`mcp` become the catch-all group. Grouping lives in src/lib/integration-groups.ts, kept free of the @site alias and of any JSON import so both consumers can use it — the theme swizzle (webpack) and sidebars-integrations.ts (evaluated at config load). An unrecognised category falls into the last group rather than disappearing from the sidebar. * docs: regenerate the docs-skill mirror for the supersede admonitions scripts/generate-docs-skill.sh mirrors docs-integrations/ into skills/; the launch commit edited seven pages without re-running it, so the mirror still described the per-agent plugins as current. * docs: spell out the migration path for Claude Code and Codex Both pages said memory "does not move automatically", which is now only half true: the server endpoint IS carried over (~/.hindsight/claude-code.json and ~/.hindsight/codex.json, same keys), so nobody is silently switched to Cloud. Each page now states what moves — the endpoint automatically, conversations via --import-conversations — and what does not: the recall/retain settings, missions and bank-naming options. It also says why conversations come from local transcripts rather than the old bank: that bank defaulted to a single static bank shared by every project, whose documents record only a session id, so attributing them to a repo requires the local transcripts regardless. These are the only two superseded plugins with an endpoint to carry; the other four pages already say their history can't be imported and are unchanged. * feat(claude-code,codex): deprecation notice in the old plugins' sessions Folded in from #3205 so the launch lands as one change: the docs that announce the Coding Agents plugin and the in-session notice that points existing users at them ship together, rather than one arriving without the other. Both plugins keep working, but they are deprecated — development has moved to @vectorize-io/hindsight-coding-agents. A changelog entry reaches nobody who installed a year ago, so the SessionStart hook says it, via systemMessage (the channel Claude Code shows the USER; additionalContext would only reach the model). Codex accepts the same hook output shape, so one design serves both. Emitted before the existing early returns: neither the memory settings nor whether the server is reachable changes the fact that the plugin is deprecated. Shown every session, with `"upgradeNotice": false` as the permanent opt-out — stated in the message itself, which is what makes that frequency acceptable. With no rate limit there is no state file and none of its failure modes; what remains is a config check that returns None rather than raising, because a promotional message must never be why a session breaks. * docs: per-harness install sections, featured hub cards, browsable sidebar Page - One subsection per harness with its logo and a copyable install command, replacing the table: the command is what a reader came for, and a table cell is not copyable. - Title is just "Coding Agents"; the old keyword-stuffed title read as spam in the sidebar and breadcrumbs. - "Ingestion internals (no CLI)" is dropped from the docs page via the existing DROP_SECTIONS mechanism, staying in the README where the contributor-facing audience is. Integrations Hub - A Featured grid pins Coding Agents, Vercel AI SDK and OpenClaw above the rest, and only on the unfiltered view — pinned cards above non-matching search results would read as noise. - The Coding Agents card draws all ten supported harness logos. "One install, every agent" is the whole pitch and a single icon cannot carry it. - Logos come from the control plane's harness set, which is already keyed by the exact harness ids the plugin uses, so the two stay consistent by construction. Sidebar - Groups are open but show six entries each, with the tail behind a nested "Show all N". Fully expanded, 59 entries were a wall; fully collapsed hid that the list was worth opening. - The umbrella Coding Agents entry leads its group instead of sorting under "C", since it is the entry point to every other agent in that list. * fix(docs): point the page's harness logos at this build, not production The README must use absolute URLs so the logos render on npm and GitHub, but the docs page inherited them verbatim — pinning every image to hindsight.vectorize.io, where /img/harness/* does not exist yet. Logos were broken locally and in previews, and would only start working after a deploy. The sync script now rewrites our own absolute asset URLs to site-relative, next to the repo-relative-link rewrite it already does for the same reason: two audiences needing different URLs from one source. * docs: curate the sidebar previews, harness logos for coding agents The coding-agent group now previews HARNESSES, not pages: ten logos that all link to the Coding Agents page. Listing ten integration pages there presented one plugin as ten separate integrations, which is the opposite of its pitch — and the logos make the group recognisable at a glance. Every individual page moves behind "Show all", which is also what keeps it associated with the sidebar. The other groups get hand-picked previews instead of the first six alphabetically — the first names in a sorted list are an accident of spelling, not a description of the group: Frameworks & SDKs — LangGraph/LangChain, Vercel AI SDK, Vercel Chat, Eve, CrewAI Apps & tools — ChatGPT, Hermes, OpenClaw, Obsidian Hermes, NemoClaw, OpenClaw and Paperclip move from framework to tool. The overflow label counts what opening it actually reveals: "Show 21 more" where some entries are already previewed above, "Show all 19" for coding agents, whose overflow really is every page. * docs: inline sidebar preview, full list on the integration pages The two sidebars do different jobs, so they now show different things. Main docs sidebar — a preview: three groups rendered INLINE and non-collapsible, nothing behind a disclosure. Ten harness logos for coding agents, five frameworks, four apps, then an "All integrations" link to the gallery, which offers search and filters a sidebar cannot. Integration pages — the full list again: flat, alphabetical, every entry. Once you are on one of these pages you are comparing and hopping between them, so hiding two thirds behind "Show N more" worked against the reader. Listing each page directly is also what associates it with this sidebar. * docs: promote the sidebar groups, separate Featured, brand the umbrella card Sidebar: the "Integrations" placeholder is replaced BY its contents instead of filled, so the three groups sit at the same level as the rest of the navigation. The wrapper was two levels of nesting to say one thing, and it indented every entry beneath it. Hub: a divider and an "All integrations" heading separate the pinned Featured cards from the full list, which otherwise read as one uninterrupted run. The Coding Agents card carries the Hindsight mark rather than the GitHub logo — it is our own package, and the GitHub icon said nothing about it. * docs: install with npx, no global install Every example across the README, the seven integration pages, the companion skill and the generated docs now runs the installer with npx. Nothing here asks anyone to keep a package installed whose only job is to wire other tools up. The paragraph telling people to install globally — and warning that npx was refused — is replaced by what actually happens: install copies what it needs into ~/.hindsight/coding-agents and points each agent's wiring there, so it does not matter where it ran from, and updating is the same command again. Depends on #3241, which makes that staging real; until it ships in 0.0.6 the published installer still refuses to run from an npx cache. * docs: move the superseded pages into a Legacy section, out of the gallery The six per-agent pages the Coding Agents plugin replaces — Claude Code, Codex, Cursor CLI, Copilot CLI, opencode, Cline — move to a `legacy` category. They keep their pages and their migration banners: people still run these plugins and still arrive from old links, so removing the pages would break both. What changes is where they are offered. The gallery is where someone comes to CHOOSE an integration, and offering one we are actively migrating them off points them at a dead end — so legacy entries are filtered out of it, including the hero banner, whose hardcoded list still advertised Claude Code and now advertises the plugin that replaced it. In the sidebar they sit in a collapsed "Legacy" section at the end instead of mixed in alphabetically, so the main list is only what we would recommend today. Docusaurus expands that section automatically when you are on one of the pages. Grouping keys off an explicit `harnessPreview` flag now: "no previewIds" used to imply the coding-agent group, which the Legacy group would also have matched.	2026-08-07 17:00:50 +02:00
Nicolò Boschi	d6bdb62a02	docs(coding-agents): generate the docs page from the README, lead with install ... The two pages described the same product in different words and had drifted: the docs page still carried install instructions that no longer worked and a harness table that had fallen behind. The README is the single source now — a sync script writes the doc page from it, and `--check` runs in the docs build so the two cannot separate again (verified: the build fails on a hand-edited page). Also, from reading it as a new user would: - Install moves above "How it works". The first question is "how do I get this", and it was buried under the harness table. - "How it works" becomes short bullets grouped by what actually happens — ingestion, what the agent receives, write-back, guarantees — instead of seven dense paragraphs. - Layout (a source-tree map for contributors) is dropped from the doc page: it answers a question no reader of the docs site is asking. - The Configuration section no longer claims "no environment variables", which stopped being true when the env fallback landed.	2026-08-03 15:29:26 +02:00
Nicolò Boschi	8e5fdf28dd	docs(coding-agents): unlist the integration page until it is announced ... The package is about to be released so it can be installed and exercised end to end, but its page should not surface yet. Three edits, each covering a different surface: - integrations.json: the entry drives BOTH the gallery and the sidebar (the sidebar is generated from this file), so removing it hides both. - `unlisted: true` on the doc page: keeps it out of search and the sitemap and marks it noindex, while leaving it reachable by direct URL — and stops the build warning about a doc belonging to no sidebar. - check-integrations.mjs EXCLUDED: the reverse check fails the docs build when a released integration has no gallery entry, so without this the build breaks the moment the release tag exists. To publish it later: drop it from EXCLUDED, restore the integrations.json entry, and remove `unlisted` from the page.	2026-08-03 11:08:27 +02:00
Nicolò Boschi	24abf373da	docs(integrations): single source of truth (integrations.json) for gallery + sidebars (#2048) ... * docs(integrations): single source of truth for sidebar + guardrails Make src/data/integrations.json the single source for the Integrations sidebar across every docs version, and add build-time guardrails so it can't drift. - Inject the Integrations sidebar category at render time from integrations.json via a DocRoot/Layout/Sidebar swizzle. Every docs version (current + frozen 0.3-0.7) now shows the same list, and adding one JSON entry is all it takes - no per-version sidebar edits. The sidebar files keep only a positional placeholder category (a link to the gallery), which the swizzle replaces. - check-integrations.mjs, wired into `npm run build`: - forward: fail if a JSON entry has no docs-integrations/<slug> page (the injected sidebar isn't covered by Docusaurus link-checking). - reverse: fail if a released integration tag is missing from the JSON (skips gracefully without tags; excludes private cloudflare-oauth-proxy). - Add the released-but-undocumented integrations to the JSON so the gallery + sidebar show them: claude-agent-sdk and superagent (with new doc pages) and paperclip. - CI: fetch tags (fetch-depth: 0) in the docs build jobs so the reverse check can see them. One name + one icon per integration come straight from the JSON; display order is the JSON array order (manual, most-interesting-first). * docs(code-review): require integrations.json entry + doc page for integrations Add a review rule: every added/released integration must have an entry in hindsight-docs/src/data/integrations.json (single source of truth for the gallery + sidebar) and a docs-integrations/<slug> page, enforced by check-integrations.mjs. Also note the changelog generator keeps its own INTEGRATIONS list that must be updated for releases. * docs(integrations): sidebar on (unversioned) integration pages + alphabetical order - Give the integration doc pages their own sidebar without versioning them: point the unversioned `integrations` plugin at sidebars-integrations.ts, generated from integrations.json (doc items so each page associates with the sidebar and renders it). Previously these pages had sidebarPath: false (no sidebar at all). - Sort integrations alphabetically by name in all three surfaces — the Integrations Hub gallery, the main docs sidebar, and the new integration-page sidebar — via a shared src/lib/integrations.ts helper (gallery + swizzle) and an inline sort in the config-loaded integration sidebar. JSON array order is no longer significant for display. - The swizzle now only fills the main-docs placeholder category, leaving the generated integration-page sidebar untouched. * docs(integrations): replace placeholder/wrong icons with official brand icons Fetch real brand icons from each integration's official site (apple-touch-icon / high-res favicon) and point integrations.json at them, replacing self-generated, generic, or reused placeholders: - New brand icons for claude-agent-sdk, superagent, paperclip, codex, grok-build, ai-sdk, chat, local-mcp, openclaw, langgraph, autogen, opencode, n8n, pipecat, smolagents, dify, strands, outsystems, pydantic-ai, and refreshed many others (litellm, crewai, perplexity, llamaindex, vapi, flowise, hindclaw, agno, hermes, agentcore, google-adk, openai-agents, roo-code, skills, claude-code). - claude-agent-sdk now uses the Claude/Anthropic brand (was reused claude-code icon); context-forge uses the MCP logo (it's an MCP gateway); superagent uses its pyramid logo (was generic package icon); paperclip its paperclip mark. - Kept the existing real marks for nemoclaw (NVIDIA NeMo) and right-agent — no official brand favicon exists for those, and the auto-fetched candidates were wrong (a letter favicon / the repo author's avatar). - Removed 7 now-orphaned icon files. * ci(docs): add explicit integrations check step to build-docs Run scripts/check-integrations.mjs as a named, fail-fast step before the docs build (the build runs it too, but this surfaces it clearly and fails before the slow build). Pure Node, no npm install; uses the tags already fetched via fetch-depth: 0. * ci(docs): trigger build-docs (integrations check) on integration changes Add hindsight-integrations/** to the docs path filter so the integrations single-source check runs on integration-only PRs (which can add/rename an integration without touching hindsight-docs/**).	2026-06-08 15:23:17 +02:00
Mr. Khachaturov	6a1d5fcd30	feat(docs): move template manifests to per-file manifest_file refs (#1066) ... hindsight-docs/src/data/templates.json holds both presentation metadata and inline BankTemplateManifest bodies. A contributor who only tweaks retain_mission has to touch a 130-line file full of metadata they did not mean to edit. Move each manifest into its own file under src/data/templates/. The catalog entry keeps the presentation fields and replaces inline manifest with a manifest_file path. The renderer uses webpack's require.context to bundle every manifest file at build time, so adding a template only needs a new file plus a catalog entry. scripts/check-templates.mjs follows manifest_file off disk. Add a "Submit a template" CTA button to the gallery banner, like the integrations page already has. Existing templates render unchanged in the Template Hub.	2026-04-15 09:19:08 +02:00
Nicolò Boschi	7990381f6a	fix(ci): resolve all CI failures (#847) ... * fix(ci): resolve all CI failures — unversioned integrations, test retries - Move integration docs to separate unversioned docs plugin (docs-integrations/) so new integrations don't need to be duplicated across versioned_docs - Remove integration pages from versioned_docs (v0.3, v0.4) — sidebar entries now use links instead of doc refs - Add missing title/description SEO frontmatter to autogen.md - Add retry logic (2 attempts) to test-doc-examples.sh for transient LLM timeouts - Add pytest-rerunfailures to test-api with --reruns 2 for flaky Gemini-dependent integration tests * ci: retrigger * fix: graph entity inheritance, SyncTaskBackend error propagation, fact_type test regressions - Fix observation entity inheritance in get_graph_data: the unit_entities query only fetched entities for visible observation IDs, not their source memory IDs, so the inheritance loop always found an empty entity_map - Remove error swallowing in SyncTaskBackend._execute_task so test failures surface instead of being silently logged - Wrap remaining consolidation submission call sites with try/except since consolidation is non-critical for those operations - Fix test_sync_backend test to expect errors to propagate - Remove fact_type=["world"] filter from test_document_upsert_behavior and test_mentioned_at_from_context_string (same PR #848 regression) - Remove flaky marker from consolidation test (now deterministic)	2026-04-02 17:17:42 +02:00
Nicolò Boschi	30a319a6ab	feat: bank template import/export with Template Hub (#819) ... * feat(api): add bank template import/export endpoints Add POST /banks/{bank_id}/import and GET /banks/{bank_id}/export endpoints for declarative bank setup via JSON manifests. A template manifest (version 1) can include bank config overrides and mental model definitions. Import creates or updates mental models matched by id, applies config as per-bank overrides, and returns async operation IDs for content generation. Export dumps a bank's explicit overrides and mental models as a manifest that can be re-imported into another bank. Includes control plane UI: bank creation dialog now accepts an optional template JSON to pre-configure the bank on creation. * docs: add Template Gallery page and bank templates reference - Template Gallery (/templates) with search, category filter, manifest preview modal with copy-to-clipboard - 5 starter templates: Customer Support, Research Assistant, Personal Journal, Code Review Buddy, Meeting Notes - Bank Templates API reference doc (developer/api/bank-templates) - Sidebar entry under API section * docs: add Template Gallery links to navbar and sidebar - Top navbar: "Templates" link between Integrations and Changelog - Sidebar: "Template Gallery" in Resources section * fix(docs): remove emoji icons, autofocus search, fix placeholder in template gallery * docs: rename to Bank Templates, move to Resources sidebar only * docs: add Bank Templates to Resources navbar dropdown * feat(api): add directives to bank template import/export - Add BankTemplateDirective model with name, content, priority, is_active, tags - Import creates/updates directives matched by name - Export includes all directives (active and inactive) - Validation: duplicate names rejected, empty name/content caught - Tests: 24 tests covering directives create/update, existing vs new bank import, validation, export with directives, full round-trip * docs: add directives to bank templates docs and sample templates * feat(api): add JSON Schema endpoint for bank template validation - GET /v1/default/bank-template-schema returns the JSON Schema auto-generated from the Pydantic BankTemplateManifest model - Static schema file at docs/static/bank-template-schema.json - Docs updated with schema endpoint, static file link, and validation examples (Python jsonschema, Node ajv-cli) * feat(api): live schema validation on import, fix schema endpoint path - Move schema endpoint to /v1/bank-template-schema (system-level, not per-bank) - Import endpoint now accepts raw JSON and validates with Pydantic manually, returning clean 400 errors instead of raw 422s for all validation failures - All validation (schema + semantic) returns consistent 400 with detailed messages * docs: add interactive JSON Schema viewer to Bank Templates page Renders the Pydantic-generated schema as a collapsible property tree with types, required badges, defaults, and descriptions. The schema is imported from the static bank-template-schema.json file. * ui: add template toggle switch and browse link to bank creation dialog - Replace always-visible textarea with a switch toggle ("Import from template") - Textarea only shows when switch is on, keeping the dialog clean by default - Add "Browse templates" link pointing to hindsight.vectorize.io/templates - Reset template state when switch is toggled off or dialog is cancelled * ui: add empty state with Add Document CTA to data view When a bank has 0 memories, the data view (all tabs: constellation, graph, table, timeline) shows a centered empty state with a CTA button that opens the Add Document dialog. * docs: replace templates with Conversation and Coding Agent Remove generic placeholder templates. Add two practical templates based on actual integration patterns: - Conversation: for chat agents (LiteLLM, LangGraph, Pydantic AI, Vercel AI SDK). Tracks user preferences, open threads. - Coding Agent: for Claude Code/Codex. Tracks technical decisions, project context, developer preferences. High literalism. * docs: rename gallery to Bank Templates Hub, keep API doc as Bank Templates * docs: register layout-template and file-json icons in navbar and sidebar * docs: register layout-template icon in DefaultNavbarItem for dropdown items * docs: show integration icons on template cards Templates now have an optional `integrations` field referencing integration IDs from integrations.json. Icons are resolved at render time and shown in the card header next to the category badge. * docs: add Personal Assistant template for OpenClaw, Hermes, NemoClaw * feat: add Export Template to bank actions + map all integrations to templates - Add "Export Template" to the bank Actions dropdown — exports config, mental models, and directives as JSON, copies to clipboard - Add export API route and client method - Map remaining integrations to templates: CrewAI, AG2, Agno, Strands, LlamaIndex, local-mcp, skills → Conversation; hindclaw → Personal Assistant * feat: add --template flag to LoCoMo benchmark + remove schema from Hub - LoCoMo benchmark accepts --template <path> to apply a bank template manifest (config, mental models, directives) before ingestion - Template is applied per-bank in both single-phase and two-phase modes - BenchmarkRunner.apply_template() reuses the same engine methods as the /import API endpoint - Remove Manifest Schema section from Bank Templates Hub page (schema stays in the API reference doc) * refactor: remove description field from bank template manifest * docs: remove tags, fact_types, and directives from starter templates * docs: remove reflect_mission and disposition fields from starter templates * build: validate template manifests against JSON Schema during docs build * cleanup: remove unused JsonSchemaViewer component * docs: remove retain_extraction_mode from starter templates * ui: enable word wrap in template manifest preview * docs: add link to Bank Templates reference doc from Hub page * docs: convert bank templates doc to mdx with multi-language code snippets - Convert bank-templates.md to .mdx with Tabs/CodeSnippet components - Add example files: bank-templates.py, .mjs, .sh, .go with doc markers - Examples cover import, dry-run, export, round-trip, and schema - Regenerate OpenAPI spec and all client SDKs (Python, TS, Rust, Go) * fix: migration revision collision + use typed models in benchmark template - Rename merge migration d6e7f8a9b0c1 -> d6e7f8a9b0c2 to resolve revision ID collision with case_insensitive_entities_trgm_index - Update a4b5c6d7e8f9 down_revision to point to the renamed migration - Fix f-string lint in case_insensitive migration - BenchmarkRunner.apply_template() now validates manifest through BankTemplateManifest Pydantic model instead of raw dict access - Remove redundant inline imports (json, Path already at module top) * fix(docs): add missing Go tab to dry-run code snippet * ci: retrigger * fix: sync skills openapi.json + fix bankId null type error in export - Copy updated openapi.json to skills/hindsight-docs/references/ - Add null guard for bankId in Export Template onClick handler * fix: sync generated files (memory_engine formatting, docs skill references) * cleanup: remove obsolete migration collision workaround	2026-04-02 12:21:53 +02:00
Chris Bartholomew	45ffc7fe90	SEO: add title and description to all integration pages (#787) ... * SEO: add title and description to all integration pages All 17 integration docs pages were missing title and description frontmatter, causing Docusaurus to generate unhelpful titles like "OpenClaw | Hindsight" and pull body text as meta descriptions. - Add keyword-rich title and description frontmatter to all integration pages in both docs/ (current) and versioned_docs/version-0.4/ - Add scripts/check-integration-seo.mjs to enforce title + description on all future integration pages - Wire the check into the build script so it runs locally and in CI * Fix missing frontmatter on docs/sdks/integrations/openclaw.md * Regenerate docs skill after integration page SEO updates	2026-03-30 17:53:43 -04:00
Nicolò Boschi	a56cd044e5	feat: 4-tab code parity across all documentation examples (#613) ... * feat: independent versioning for integrations - Add per-integration changelog pages at /changelog/integrations/<name> - Move main changelog to changelog/index.md (URL unchanged) - Add --integration flag to generate-changelog for LLM-based per-integration changelog generation - Add scripts/release-integration.sh <name> <version> for cutting integration releases - Add .github/workflows/release-integration.yml to publish on integrations/** tags - Remove integrations from main release.sh and release.yml cycle * fix: add agno and hermes integration docs to version-0.4 for production build * chore: apply ruff formatting to generate_changelog.py * feat: add 4-tab code parity across all documentation examples Every code snippet Tabs block now has Python, Node.js, CLI, and Go variants. Raw HTTP/curl tabs replaced with proper SDK calls. New example files: - Go: retain.go, recall.go, reflect.go, memory-banks.go, directives.go, mental-models.go, documents.go, main-methods.go - Shell: memory-banks.sh, directives.sh, mental-models.sh - Node.js: mental-models.mjs Extended example files with missing sections: - recall.mjs/sh: world/experience/observation types, token-budget, all tag modes - reflect.sh: reflect-with-params, reflect-disposition, reflect-sources, reflect-with-tags - reflect.mjs: reflect-with-tags, fixed reflect-sources API usage - retain.mjs/sh: retain-conversation, retain-batch, retain-files-batch SDK/CLI additions: - TypeScript: getMentalModelHistory method - CLI recall: --tags, --tags-match flags - CLI reflect: --tags, --tags-match, --include-facts flags - CLI directive update: --is-active flag - CLI bank set-config: --retain-mission, --retain-extraction-mode, --observations-mission, --reflect-mission, --disposition-* flags Build validation: - scripts/check-code-parity.mjs validates 4-tab parity across all MDX files - Integrated into npm run build — fails if any Tabs block is missing a variant * fix: fix doc examples for Go, Node.js, CLI + add mental model with-id examples - Fix Go Budget constants: BUDGET_HIGH/LOW/MID → HIGH/LOW/MID - Fix Go documents.go: ListDocuments returns []map[string]interface{}, use map access - Fix Go retain.go: use correct relative path for sample.pdf - Fix Node.js createMentalModel: use positional args (name, sourceQuery) not object - Add CLI 'history' subcommand for mental models (api.rs, main.rs, mental_model.rs) - Rebuild TypeScript/Python clients to support id param in createMentalModel - Add create-mental-model-with-id examples across all 4 languages and docs * fix: move id param to end of create_mental_model signature for backwards compat	2026-03-19 11:31:51 +01:00
Nicolò Boschi	47be07f97f	bump pg0 0.11.x and improve documentation (#33) ... * bump pg0 0.11.x and improve documentation * bump pg0 0.11.x and improve documentation * bump pg0 0.11.x and improve documentation * ci: test notebooks on ci * ci: test notebooks on ci * rm llms-full from repo * formatting * formatting	2025-12-16 13:33:01 +01:00
Nicolò Boschi	4191597098	add llms.txt	2025-12-10 13:51:21 +01:00