v0.3.9

Highlights

• Ships a refreshed site and not-found experience, including updated homepage content structure and navigation/sidebar behavior.
• Expands CLI init configuration and environment-targeting support, plus stronger config path handling.
• Adds new developer docs for onboarding, installation, Docker usage, and memory failure modes/interactions.

Testing and Reliability

• Adds/updates targeted CLI, config, site-data, and Playwright tests for the new behavior.
• Stabilizes Playwright site coverage startup by aligning fixture UI startup with the configured Playwright base URL port.

Included Commits

• c966806 Release v0.3.9.
• ec99f96 Fix Playwright site coverage test startup.

v0.3.8

Highlights

• Fix npm package install resilience by shipping openapi.yaml and introducing shared OpenAPI file resolution that works outside source checkouts.
• Keep MCP stdio streams safe by moving schema registry informational logs off stdout.
• Improve CLI init context detection for package-consumer projects using installed neotoma in the current working directory.
• Add release-safety contract coverage for package contents and stdio logging behavior, plus integration adjustments for credential-related unstructured store edge cases.
• Include minor UI polish for section navigation tooltips in the sidebar.

Validation

• vitest suite executed via pre-commit hooks during release commit.
• Targeted contract and regression tests passed locally, including OpenAPI install resilience and stdio logging safety.

Release v0.3.7

Patch release focused on CLI startup behavior, onboarding guidance, and site/update alignment.

Highlights

• Improved CLI startup and environment handling behavior across local workflows.
• Added and updated onboarding documentation to better guide first-run agent setup.
• Applied post-hook CLI/init test updates and refreshed generated site output artifacts.

Documentation updates

• Expanded developer-facing setup and onboarding docs, including CLI configuration guidance and onboarding flow documentation.
• Refined MCP/CLI instruction docs and related getting-started/release checklist material.

Included commits

• 013f097 — Release v0.3.7.
• ac5e363 — Apply post-hook updates to CLI init and site build artifact.
• 9dc73b2 — Update CLI startup docs and environment handling.

Notes

• GitHub release tag: v0.3.7
• Release branch target: release/v0.3.3

v0.3.6

Highlights

• Improves mobile table rendering while preserving desktop table styling.
• Expands CLI initialization behavior and startup UX coverage.
• Adds VM testing documentation and refreshes setup/release docs.

Key Changes

• Frontend: updates table and site page behavior for mobile layout polish (frontend/src/components/SitePage.tsx, frontend/src/components/ui/table-scroll-wrapper.tsx).
• CLI/Core: substantial updates in CLI command flow and MCP config scanning (src/cli/index.ts, src/cli/mcp_config_scan.ts, src/cli/config.ts).
• Tests: adds and updates init/session tests to validate init targeting and interactive flows (tests/cli/cli_init_commands.test.ts, tests/cli/cli_init_interactive.test.ts, tests/cli/cli_session_startup_ux.test.ts).
• Docs: updates developer docs and adds docs/developer/macos_vm_testing.md.
• Assets: includes demo asset frontend/src/assets/thinking-and-planning-demo.gif.

Upgrade Notes

• No manual migration steps required for typical installs.
• If you use custom CLI initialization flows, review updated init behavior and CLI docs.

Full Changelog

v0.3.5...v0.3.6

Release v0.3.5

Highlights

• Refresh docs site get-started flow with a unified tool-agnostic walkthrough and single clickable screen recording.
• Improve docs table UX and visual consistency (full-width tables, rounded borders, mobile behavior, scroll hint logic).
• Update Docker packaging/runtime docs and snippets for CLI + MCP usage from containerized deployments.

Validation

• Passed: npx vitest run src/site/site_data.test.ts
• Passed via pre-commit hooks: type-check, lint, tests, e2e, docs dependency validation.

v0.3.4

Highlights

• Fix retrieve_entities for entity_type: \"task\" to paginate after deleted-entity filtering.
• Align total with visible (non-deleted) entities so pagination offsets remain consistent.
• Add regression coverage for task pagination/count consistency.

Included changes

• src/services/entity_queries.ts
• src/shared/action_handlers/entity_handlers.ts
• tests/integration/mcp_entity_variations.test.ts

v0.3.3

What Changed

CLI reliability for npm-installed usage

• Added fallback Neotoma path resolution from the installed CLI location so commands work from arbitrary working directories.
• Updated CLI repo/path resolution flow to better support shells where no source-checkout cwd is present.

Terminology and UX clarity

• Reworded user-facing CLI messaging to distinguish:
  • Neotoma path (configured runtime path)
  • Neotoma source checkout/root (source-required workflows)
• Removed ambiguous "repo" phrasing in prompts, status panels, and error guidance where it confused npm-installed users.

Docs alignment

• Updated CLI and runbook documentation to match the new terminology.
• Updated init/env troubleshooting/test instructions so expected output strings match current CLI behavior.

Frontend/content updates

• Included current in-branch frontend content updates already staged in this release.
• Normalized related-post ordering in site data and added a targeted assertion in frontend tests.

Behavior Changes

• neotoma commands that depend on path resolution behave more reliably when run outside a source checkout, including VM/remote shell contexts.
• User guidance now refers to "Neotoma path" and "source checkout" instead of generic "repo" wording.

Internal Changes

• Added/updated CLI tests to reflect updated path-resolution behavior.
• Added frontend assertion to guard related-post ordering expectations.

Fixes

• Fixed path-resolution failures that could surface as setup/init guidance even after install in non-repo working directories.

Tests and Validation

• Pre-commit validation suite passed for both commits on release/v0.3.3.
• Ran frontend tests: npm run test:frontend.

Breaking Changes

• None identified.

Deployment Note

• This release is created from release/v0.3.3 branch. GitHub Pages deploy workflow remains untouched because no push to main was performed.

v0.3.2

What Changed

CLI and Initialization Reliability

• Fixed neotoma init behavior to correctly create .env when repo context is established later in the flow, including runs launched outside the repo.
• Improved no-command CLI guidance and environment/configuration status messaging in src/cli/index.ts.
• Added explicit tester guidance for this fix set in docs/testing-instructions-init-env-fix.md.

Site and Documentation Delivery

• Updated site content/SEO and generated docs/site assets:
  • frontend/src/components/SitePage.tsx
  • frontend/src/site/site_data.ts
  • frontend/src/site/seo_metadata.ts
  • frontend/index.html
  • frontend/docs.html
  • scripts/build_github_pages_site.tsx
  • docs/assets/neotoma_banner.png

Runtime and Service Hardening

• Applied small but broad service/runtime updates across API and MCP-related modules:
  • src/actions.ts, src/server.ts, src/mcp_ws_bridge.ts
  • src/services/mcp_auth.ts, src/services/mcp_oauth.ts
  • src/services/field_validation.ts, src/services/field_converters.ts
  • src/services/parquet_reader.ts, src/services/public_key_registry.ts
  • src/crypto/auth.ts

Packaging and Release Hygiene

• Updated package metadata/version state in package.json and package-lock.json.
• Updated release/deployment docs and status artifacts.

Behavior Changes

• neotoma init now more reliably creates and reports .env setup outcomes.
• Running neotoma without command/context provides clearer actionable guidance for missing repo/env configuration.

Internal Changes

• Refined site build and deployment-related content generation.
• Included supporting documentation and release/process cleanup tied to these fixes.

Fixes

• Resolved .env creation edge case during interactive init.
• Improved env/config status visibility in CLI initialization output.

Tests and Validation

• Added a dedicated tester checklist for init/env behavior verification.
• Updated related docs and release validation references.

Breaking Changes

• None identified.

v0.3.1

What Changed

CLI and Setup

• Improved CLI initialization and startup behavior in src/cli/index.ts, including richer setup/status handling used during neotoma init and startup flows.
• Expanded environment defaults in .env.example to better align local setup with current runtime expectations.

Frontend and App Boot

• Updated frontend boot wiring in frontend/src/main.tsx and frontend/src/components/MainApp.tsx.
• Added analytics utility support in frontend/src/utils/analytics.ts and related typings in frontend/src/vite-env.d.ts.

Release and Infrastructure Tooling

• Added release safety checks and process guidance in docs/developer/pre_release_checklist.md.
• Added release/deployment helper scripts for Cloudflare and publish validation:
  • scripts/check_bundlephobia.js
  • scripts/cloudflare_ensure_caa_letsencrypt.sh
  • scripts/cloudflare_set_dns_only.sh
  • scripts/cloudflare_set_github_pages_apex.sh
  • scripts/remove_cloudflare_redirect.sh
• Updated deployment guidance in docs/infrastructure/deployment.md.

Packaging and Dependency State

• Updated package.json and package-lock.json for release packaging and dependency alignment.
• Updated rule-distribution copies for CLI instructions (.cursor, .claude, .codex).

Behavior Changes

• neotoma startup and initialization paths are more explicit and consistent during first-run configuration.
• Frontend bootstrap and telemetry integration behavior were updated for site/app runtime.

Internal Changes

• Strengthened pre-release and deployment process assets to reduce release risk and improve repeatability.
• Added supporting shell tooling for DNS/domain and release health workflows.

Fixes

• Setup and startup edge cases in CLI initialization flow were addressed.

Tests and Validation

• Maintained CLI command coverage guard updates in tests/cli/cli_command_coverage_guard.test.ts.
• Added pre-release validation checks and publish quality guardrails.

Breaking Changes

• None identified.

v0.3.0 developer release

Highlights

• Developer release focused on production domain cutover and release operations.
• GitHub Pages deployment switches from dev to main.
• Canonical site URLs move from https://markmhendrickson.github.io/neotoma/ to https://neotoma.io.
• Release preflight is green on type-check, build, tests, and install simulation.

Full functionality audit summary

• API surface: OpenAPI currently contains 61 path entries.
• CLI surface: includes auth, store/upload, entities, sources, observations, relationships, timeline, schemas, stats, snapshots, request passthrough, and MCP setup flows.
• MCP surface: includes store/retrieve/query/mutate actions for entities, observations, relationships, schemas, interpretations, and auth.
• Web/docs surface: static site includes install, terminology, API/MCP/CLI capability tables, and setup guidance.
• Storage/runtime surface: local SQLite-first flow, source file storage, backup/logging commands, and API server runtime controls.

Changes in this release

Infra and deployment

• Pages workflow trigger changed to main.
• Deployment guide updated for main publishing and direct neotoma.io serving.
• Cloudflare redirect-removal checklist added for apex cutover.
• Developer workflow doc includes guidance to disable Cursor commit attribution trailer.
• CLI output wrapping now prefers path and word boundaries for cleaner terminal formatting.

Domain reference migration

• Replaced all https://markmhendrickson.github.io/neotoma/ references with https://neotoma.io in:
  • frontend site metadata
  • frontend/public/site_pages index.html
  • robots/sitemap files
  • SEO unit tests

Tests and verification

• tests/unit/seo_metadata.test.ts passes with updated canonical domain.
• Full test suite pass: 89 test files passed, 2 skipped; 1054 tests passed, 12 skipped.
• npm run simulate:install passes end-to-end.

Breaking/operational changes

• Marketing site deployment source branch is now main.
• Canonical domain references now target https://neotoma.io.
• Cloudflare forwarding to GitHub Pages URL must be removed to avoid redirect loops/mixed canonical behavior.

Known blockers before final cut

• npm whoami currently returns 401 Unauthorized, so npm publish cannot run until registry auth is configured.
• External infrastructure tasks (Cloudflare rules + GitHub Pages custom-domain enforcement) require dashboard access and confirmation.

Release sequence after approval

1. Confirm this version and notes.
2. Fix npm auth, publish v0.3.0.
3. Merge dev to main.
4. Verify Pages deploy from main.
5. Tag v0.3.0 and create GitHub release.