fragmentation/git + hex publish workflow#1
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Mara <mara@systemic.engineer>
systemic-engineer
added a commit
that referenced
this pull request
Jun 2, 2026
Tests reference types and behaviours that DON'T compile yet — the GREEN commit's job is to make them green. Per docs/specs/fragmentation-mcp.md §3.4 (shard sub-tools), §4 (HamiltonScheduler at the agent altitude), §9 T2 (scope + acceptance). What the new tests pin: 1. `ShardId(uuid::Uuid)` newtype — no bare UUIDs cross the wire. 2. `BudgetMb(u64)` newtype — no bare megabytes cross the wire. 3. The four `fragmentation.shard.*` sub-tools (open/status/flush/close) dispatch as separate wire callables — refinement #1 from the T1 report. 4. `TWELVE_TOOL_NAMES` becomes `FIFTEEN_TOOL_NAMES` (11 + 4 sub-tools). The §3.6 row count is still twelve CATEGORIES; the wire callable count is fifteen. Spec §3.6 needs a small upsert in GREEN. 5. `Mcp::dispatch_line` ticks the named shard's `HamiltonScheduler` before routing — observable via `tick_count` in `shard.status`. 6. `shard.close` removes the shard; subsequent ops with the same id return `ERROR_INVALID_PARAMS`. 7. The binary is now `frgmnt`, not `fragmentation-mcp` (Alex's directive). 8. `ToolRegistry::with_twelve_tools` → `with_default_tools` (it's no longer twelve). The scaffold + binary_stdio integration tests update in lockstep: scaffold.rs swaps `TWELVE_TOOL_NAMES` for `FIFTEEN_TOOL_NAMES` and adjusts the `tools/list` count assertion to 15; binary_stdio.rs renames the binary to `frgmnt` and adds a `shard.open` round-trip. [substrate-pull:realize] — the shard surface is wire binding; the capability (FrgmntStore, HamiltonScheduler) lives in the substrate. The realization is at the right altitude. GPG: -c commit.gpgsign=false per the brief's signing seam. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fragmentation/git—write(fragment, dir)writes a Fragment to disk as a content-addressed file (SHA-named, under a caller-supplied directory). No opinion about where — the caller decides. TDD arc: red then green.gleam hex publish --yes. Usesnix-setup+HEXPM_API_KEYmapped from org secretHEX_API_KEY.Test plan
🤖 Generated with Claude Code