kami
6c92f85d10
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>
956 B
956 B
How to contribute
We definitely welcome patches and contribution to this project!
Tips
Commits must be formatted according to the Conventional Commits Specification.
Always try to include a test case! If it is not possible or not necessary, please explain why in the pull request description.
Releasing
Commits that would precipitate a SemVer change, as described in the Conventional
Commits Specification, will trigger release-please
to create a release candidate pull request. Once submitted, release-please
will create a release.
For tips on how to work with release-please, see its documentation.
Legal requirements
In order to protect both you and ourselves, you will need to sign the Contributor License Agreement.
You may have already signed it for other Google projects.