feat(ecosystem): compliant Praxis/Hexis integration + vendored build

kami/Maven

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>

This commit is contained in:

kami

2026-07-19 19:32:05 +04:00

parent 0c65387a5f

commit 6c92f85d10

2071 changed files with 3915438 additions and 61 deletions

									
										vendor/github.com/dustin/go-humanize/humanize.go
									
GeneratedVendored

		+8
		
												View File
												
				@@ -0,0 +1,8 @@

				/*

				Package humanize converts boring ugly numbers to human-friendly strings and back.

				Durations can be turned into strings such as "3 days ago", numbers

				representing sizes like 82854982 into useful strings like, "83 MB" or

				"79 MiB" (whichever you prefer).

				*/

				package humanize