7 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	95fabbfcde	Forge bridge: the gate's merges and owed acts are the seat's types and the delivery client's, the version and the repository check the keys' and the trunk's; the holders and buckets it names are its own constants checked against its manifest (D-11; ADR 0634 §1, §2; issue 1966) ... Claude-Session: https://claude.ai/code/session_01NcbgfFSnn24M3GcqttoU7i	2026-11-05 16:13:00 +01:00
jschoubben	1cda01b869	Merge main (take-in #153, #154) into the registry milestone's join (D-0; issue 1966)	2026-11-05 14:16:17 +01:00
jschoubben	655791b8a3	Bridge tool test: the merged-message rows are a subtest of the existing tools test, within the test budget (issue 1585) ... Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-05 11:42:10 +01:00
jschoubben	0605962960	Forge bridge: bridge_merged_message answers a merge's merged message again, built as the bridge builds the one it publishes (issue 1585) ... Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-05 11:34:04 +01:00
jschoubben	7b7096f37e	Take-in, review round 1: no claim left behind, no sleep at the start, waits seeded at a restart, ends asked readable (issue 1585, ADR 0633) ... - A take-in releases its claims (compare-and-set, only while the claim is still its own) on a lost claim, on a claim it cannot read back, and on a merge it fails to take in: a claim left behind refused every later take-in until a restart. T5 row with a store that fails once, both ways. - The start step waits for nothing: with the build it runs unknown it says so and the forge consumer starts; a merged message left unacknowledged asks the build again (clause 1). T10 row: the start answers at once and takes nothing in. - A toolchain report evaluates pending again (ToolchainReported), since the build a revision names moves with the toolchain. T7 row: the revision is taken in once the report makes it name the running build. - The group's end is told by its whole subject (process.ModuleStreamSubject), so a repository named forge/group is never taken for one; row in the indexer's handle test. - The watchman asks the indexer's waits through indexer_pending at its start (invokes), before its durable consumer, which does not hear again what it acknowledged before a restart; the comment that said the whole stream is heard is corrected. W2 row: a wait seeded within its bound is raised past it. - bridge_groups names each group's last end ask, its who, why and when, and the bridge's answer (state end-asks). - The check's words for the indexer's rules: the trunk's manifest validator. - The bridge's end drops the merged-state test its merge commit already implies. - Test budget: groupask_test folded into groups_test, and the K1 mesh/check test into the owed status one: 804 unit tests (was 806). Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-05 00:28:56 +01:00
jschoubben	ad9a353484	Forge bridge: bridge_groups and bridge_group_end_again, the end said again through the state end-asks (issue 1585, ADR 0633 §4) ... Claude-Session: https://claude.ai/code/session_01JG73KG7AfSdh6FP8VrBqCn	2026-11-04 23:17:27 +01:00
jschoubben	bd13302ecf	DLV-FB1: the forge bridge says a branch's end as branch-deleted and answers bridge_tags ... The bridge consumes the forge module's forge.delete and writes a branch-deleted message on FORGE for a deleted branch (never the trunk, never a tag), so the builder removes the branch's tagged versions (design 51 *The forge bridge says a branch's end*). Only the forge module's account may say forge.delete: the bus refuses it from another (a case of the bridge's whole-module test). bridge_tags, served by a new tools bundle, answers a package's git tags by prefix through the forge module's gitea_api, for the builder's floor. One unit test merged into another, so the tags test adds no function (test budget). Claude-Session: https://claude.ai/code/session_01JG73KJNrH5EgFXMKKYSrig	2026-11-04 11:44:53 +01:00