Tags: ForestHubAI/edge-agents
Tags
chore: regenerate engine bindings after deploymentId description edit The contract's deploymentId description was shortened but types.gen.go was not regenerated, drifting the committed Go binding from contract/engine.yaml and failing the CI drift check. Regenerate to bring them back in sync. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
fix: relocate engine memory dir to /var/lib/foresthub/memory Move the memory working-copy dir from /var/forest to the FHS-standard /var/lib/foresthub/memory, kept in sync across the Dockerfile, the engine config default, and the CLI's generated compose. The Dockerfile now stages the mount point and copies it with nonroot (65532) ownership so the named engine-memory volume inherits writable permissions on first use — a distroless nonroot container otherwise cannot write to a root-owned mount point. Document the volume's persistence and the bind-mount alternative in the generated README.