Files
kami 6c92f85d10 feat(ecosystem): compliant Praxis/Hexis integration + vendored build
Bring the Nexus/Praxis/Hexis integration in line with
MAVEN_ECOSYSTEM_ARCHITECTURE.md:

- Praxis over HTTP: drop the in-process praxis.db open (praxisstore/
  praxistools) and call praxisd's /api/v1/tools/* API via a new praxisClient.
  Honors the "no component reads another's DB" invariant (AC#12).
  PraxisConfig.DBPath -> URL.
- Hexis confirmation gate: mutating capabilities (ReadOnly=false) now park a
  bound pendingHexis confirmation and require a spoken "да" before executing;
  read-only run immediately (AC#7, no auto attention->action).
- Capability safety: >1 verb match is ambiguous -> ask instead of firing the
  first; ambiguous Nexus resolution asks for clarification (AC#2).
- Correlation IDs on Hexis execute, recorded in the cross-service trace.
- Bug: importance arrives as JSON float64 over HTTP, not int.
- Tests: confirm-gate, decline, read-only, and ambiguity paths.

Build: vendor/ bakes in the hexis client (replace-directed at a sibling repo
outside the Docker context); Dockerfile builds from vendor and no longer
`go mod download`s the unreachable replace paths.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-19 20:24:33 +04:00

1.1 KiB

Contributing to this repository

Thank you for your interest in contributing! To help keep the project stable across its many targets, please follow these guidelines when submitting a pull request or merge request.

Verification

Before submitting your changes, please ensure that they do not break the build for different architectures or build tags.

Run the following script in your local environment:

    $ ./build_all_targets.sh

Please verify that all targets you can test pass before opening your request.

Authors and Contributors

If you would like yourself and/or your company to be officially recognized in the project:

  • Optionally, please include a change to the AUTHORS and/or CONTRIBUTORS files within your merge request.

The Process

  • Fork the repository (or host a public branch if you do not have a gitlab.com account).
  • Implement your changes, keeping them as focused as possible.
  • Submit your request with a clear description of the problem solved, the dependency improved, etc.

We appreciate your help in making the Go ecosystem more robust!