Skip to content

P0: Agent work coordination lock #68

Description

@geromet

Purpose

Central coordination point for concurrent PZTools fleet work. This is not implementation backlog. Actual default branch is master.

Absolute authority boundary

Fleet/manual agents may create, update, review, merge and consolidate work only on NON-DEFAULT branches. They must never merge any branch or PR into master. Final default review/merge belongs exclusively to Gerome's coding-agent/human workflow.

Claim protocol — two phase

Before overlapping mutation, refresh this issue body + recent comments, target issue/PR, current master, target/stable head; post one concrete 🔒 CLAIM with lane, unique run=<token>, exact issue/PR/branch/package/seam and head SHA where practical; immediately reread comments. Earlier GitHub comment ID wins overlaps. Later claimant edits its own comment to 🔓 RELEASED and chooses independent work. Two failed acquisitions => back off. Release the same claim when work stops.

Head CAS

Before every remote branch/PR/stable mutation compare the current head to the expected SHA. Unexpected movement => stop and reconcile. Never force-push through a coordination race.

Current live state — 2026-09-05 13:54 Europe/Amsterdam

Current master: f015a0b5593331186cc410831e8e05f80d80824e after Gerome merged #75.

Open fleet PR pressure: 1/5.

Current Gerome-facing rollup — #78

PR #78 is the single review surface from NON-DEFAULT fleet/stable/project-reference-layers @ 17a2b27ff0b385cda877aca2cb4c4821304d7f71.

Absorbed packages:

Exact proof retained by the stable:

The fleet merged #76/#77 only into the explicit NON-DEFAULT stable. It must not merge #78 into master; final review/merge belongs to Gerome.

Completed foundations — do not recreate

#54 remains closed completed. Remaining selected-mod requirements are canonical in #51.

Remaining #51 frontier

Continue through the existing project/reference-layer workstream rather than recreating foundations:

  1. installed/manual mod discovery and selection UI;
  2. parser/load orchestration for enabled selected roots;
  3. collision-safe project-owned aggregation/routing before imported definitions can become editable;
  4. reorder/deselect/reopen end-to-end behavior;
  5. expanded imported-write/symlink/path negatives once routing exists.

Independent evidence frontier

Capacity / stable topology

Default capacity is up to five independent implementation packages and five open fleet PRs; five is not a quota. Before a sixth, extend compatible work, use a bounded NON-DEFAULT stable branch, do proof/research/issue compaction, or move repos. Never merge a stable rollup into master.

Verification / safety

Prefer executable proof: real NLua parser→writer→parser fixtures, real filesystem ownership/path negatives, hosted CI, and representative Build-42.20 data. Missing safely obtainable tooling is agent work, not a human blocker.

Outside-contributor/human branches must never be overwritten, retargeted or closed by the fleet.

Human blockers

None evidenced.

Done when

Keep this coordination issue open while concurrent lanes exist; close only if concurrency is removed or replaced by stronger mechanical coordination.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions