Skip to content

feat(crew-log): make the conductor pull-forward a keyed bus subscriber - #16076

Merged
chenmingwei23 merged 2 commits into
mainfrom
feat/conductor-wake-bus-subscriber
Oct 3, 2026
Merged

chenmingwei23 merged 2 commits into
mainfrom
feat/conductor-wake-bus-subscriber

Conversation

@chenmingwei23

@chenmingwei23 chenmingwei23 commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A conductor is pulled forward when its worker reports because the work ledger -- a crew-log fold -- published that it moved, through the same bus every other consumer of a fold will use.

#12781 landed the pull-forward as a consumer hard-wired into the crew-log eager drain: eager.py _push_conductor_wakes imported conductor_wake and read the work-ledger binding file for every work/recorded wake. That named one consumer inside the producer, and it needed a store-import allowlist entry (_PERMITTED_STORE_IMPORTERS) the work ledger had to argue for. A second consumer of the same news (a dynamic dashboard, a card trigger) would have meant a second hook in eager.py. #15781 then shipped crew_log.bus, which publishes every advanced fold as FoldAdvanced(scope, key, fold, revision, value, seq); the work fold's key is the conductor's own board.

Why it matters

Left as is, the crew log carries a hand-wired exception to its own bus, and the next fold consumer either copies the hook or waits for this swap. The decision recorded on 2026-10-01 was to wait for #15781 and swap, rather than land the hook on main and change eager.py twice.

Not a goal

  • Changing the gate: probes/work_ledger.py, ledger_wake.py, both caps and the slow poll are untouched.
  • Carrying triggers 2 and 3 (worker session closed, worker turn ended) on the bus: neither advances the conductor's work fold, so they stay as direct hooks and read the binding file, as before.
  • A delivery guarantee for the push: the bus retains nothing, and the scheduled tick remains the fallback, as before.

What changed (motivation → approach → change)

Symptom: eager.py knew the conductor existed. Root cause: the pull-forward was wired as a second consumer of the eager drain, before the bus existed. Why this matters for the fix: an unkeyed subscriber would be handed every fold event the folder publishes, for every board and session, and #16149 has since given the bus keyed filters, a disposer and baseline=True. Change:

part before after
crew_log/eager.py calls _push_conductor_wakes per batch folds and publishes only; no import of conductor_wake
subscription none (direct call) one per watched board: (slot, <board>, "work"), baseline=True
lifecycle n/a joined at AutoNudgeService.start and on every loop-table change (the service's observer hook); disposed when the loop ends or the service stops
the board as it stood before the first event n/a the subscription's baseline, recorded as first sight; it pushes nothing
which item reported binding lookup per entry diff of each item's report stamp (last_report_at plus a digest of what the report wrote) against the last board seen
worker -> conductor lookup (close, turn end) read_binding read_binding, unchanged
gate and caps unchanged unchanged: 12 pull-forwards per item per hour; the gate spends a turn only on done / blocked / question

conductor_wake.sync_subscriptions(svc) walks the loop table once, disposes boards whose work-ledger loop ended, and starts a join for each new one. The join runs bus.subscribe(..., baseline=True) on a worker thread (the baseline read is file I/O). The baseline is the board's first sight and pushes nothing: what landed before it is the loop's own tick's to read, and at boot start() already arms every work-ledger loop at delay zero for that. A join that completes after stop sees a bumped generation and disposes what it got. The registry and the subscriptions are bounded by the same predicate, the live work-ledger loops. The fold name comes from work_vocab.WORK_FOLD_NAME instead of a local spelling.

The report stamp joins last_report_at with a digest of every field a report writes (status, summary, artifacts, pr) and the newest report event id. last_report_at has whole-second resolution and a report event id is content-addressed over status and summary, so either alone can stay unchanged across two reports in one second.

Earlier review findings:

  • Opus BLOCKING on 57d6d7a8 (registry unbounded): every loop-table change sweeps the registry and disposes the subscription of any board whose loop ended. test_a_disposed_subscription_wakes_nothing, test_a_board_whose_loop_ended_is_swept_on_the_next_observation.

  • Opus finding on 57d6d7a8 (closed item reclaims a worker): the worker map it described is gone; read_binding is repointed on every bind.

  • GPT 5.6 BLOCKING on 825cd8db43 (stale fold redirects a direct wake): the fold-fed worker map is gone; close and turn end read read_binding, the one authoritative record.

  • GPT 5.6 findings on c2ef33f95f and afa9251456 (two reports in one second push once): the stamp digests every report field plus the newest report event id. test_two_reports_in_one_second_each_push, test_a_same_second_report_with_the_same_event_id_still_pushes_on_new_fields.

  • First Principles item 8 on afa9251456 (sync_subscriptions returned join tasks no caller awaited): it returns nothing; the tests read the pending joins from _subscriptions.joining.

  • Opus finding on 825cd8db43 (the baseline's first-sight push lands in the boot tick and buys a second cycle): first sight pushes nothing. test_the_first_board_seen_records_and_pushes_nothing.

  • First Principles item 6 (WORK_FOLD duplicate): deleted; work_vocab.WORK_FOLD_NAME is imported.

  • First Principles item 4 on 889cf7d5 and item 3 on c2ef33f95f (worker map duplicates read_binding): the map, the prime and _read_board_items are deleted; triggers 2 and 3 call read_binding again, and conductor_wake.py is back on _PERMITTED_STORE_IMPORTERS for that one read.

  • src/kiro_crew/conductor_wake.py: per-board keyed subscriptions, report-stamp registry, read_binding for the loop-side triggers

  • src/kiro_crew/crew_log/eager.py: _push_conductor_wakes removed

  • src/kiro_crew/autonudge.py: install at start(), dispose_all at stop()

  • test/test_work_ledger.py: the _PERMITTED_STORE_IMPORTERS entry for conductor_wake.py now names the close and turn-end lookup only

  • docs/request-for-change/rfc-crew-log-wake.md, docs/system-specs/modules/crew-log-projection.md

Backwards compatibility

Compatible: nothing main accepts is rejected or renamed at any external surface. conductor_wake.fire_for_worker_slot_from_thread and eager._push_conductor_wakes are removed; the only caller of the first was the second.

Reader: src/kiro_crew/crew_log/eager.py:_push_conductor_wakes -- chat -- removed with it; the bus subscription replaces the call (test_a_workers_report_wakes_its_conductor_through_the_bus)

Tests

test/test_conductor_wake.py runs the real path for the bus side: a crew log on disk, the real append, the eager folder's own thread folding and publishing, the bus routing by key, and the callback scheduling onto a real event loop. Only the service is a stub.

  • test_a_workers_report_wakes_its_conductor_through_the_bus: a worker work_report append wakes the bound conductor's loop within the one eager batch that folds it.
  • test_only_the_watched_boards_work_fold_reaches_the_subscriber: another board's report, and every session-scoped fold the same writes advance, never reach the module; one wake for the watched board only.
  • test_a_disposed_subscription_wakes_nothing: loop ends, sync disposes, the bus has 0 subscribers, a later report wakes nothing.
  • test_the_first_board_seen_records_and_pushes_nothing, test_two_reports_in_one_second_each_push, test_a_same_second_report_with_the_same_event_id_still_pushes_on_new_fields, test_the_report_fields_this_module_digests_are_the_folds.
  • test_the_service_stop_disposes_every_subscription, test_a_join_that_lands_after_stop_keeps_nothing, test_the_service_start_installs_one_observer.
  • The close and turn-end trigger tests read the binding through a real work-ledger store, as on main.
  • test_the_eager_folder_names_no_conductor: the folder's source imports and references no conductor_wake.

Mutations, each run against the file and reverted:

  • subscribe unkeyed (drop scope / key / fold / baseline): 3 failed.
  • re-add a conductor_wake call inside the eager batch loop: 1 failed (test_the_eager_folder_names_no_conductor).
  • report stamp back to last_report_at alone: 1 failed (test_two_reports_in_one_second_each_push).
  • digest only the event id, not the report fields: 1 failed (test_a_same_second_report_with_the_same_event_id_still_pushes_on_new_fields).
  • first sight pushes again: 7 failed, including the three restart tests.

Local, on this head: test_conductor_wake.py, test_work_ledger.py, test_crew_log_bus.py, test_probe_work_ledger.py, test_autonudge.py, test_autonudge_reconciler.py, test_autonudge_start_failures.py, test_autonudge_refactor_contract.py, test_autonudge_dashboard_fire.py, test_monitor_controller.py: 1084 passed. mypy (Success: no issues found in 3 source files), flake8, isort, black check, comment-history, sync-io-in-async and loop-bound-locks checks exit 0.

Manual verification

The pod QA run (S1-S8 x3, from the #12781 / #15691 work) was on the earlier unkeyed head and is not repeated on this one. The bus side is covered end to end by the real-path tests above; the gate and caps are unchanged.

Related Issues

Follow-ups, not in this PR:

  • Triggers 2 and 3 (worker session closed through close_slot in dashboard/chat_handlers.py, worker turn end through notify_turn_complete in autonudge_service/timers.py) are still direct calls into conductor_wake. Moving them onto the bus needs a fold or event those paths publish.
  • The baseline-as-first-sight costs one quiet probe tick each time a work-ledger loop is armed. If that shows up in the probe budget, the bus could mark baseline deliveries so a subscriber can tell them from pushes.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

@chenmingwei23
chenmingwei23 requested a review from a team as a code owner October 2, 2026 06:23
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Fable 5) — ✅ PASS

Design-level review of c279226c12c7feadd284704f1512419d73d65df4 — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

Design-Verdict: PASS

Verify loop-table emits always run on the service loop — _on_loop_table_change silently skips the sync otherwise, leaving a newly armed board tick-only until the next on-loop emit.

[DESIGN-REVIEWED] c279226

Description read

[DESCRIPTION-READ] f532793f6f0a0a98a5ff2ed71533be10fa48b59b23ac6eda1c85fc3bab2c3214

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Fable 5) — 🟡 CONCERNS

Premise-level review of c279226c12c7feadd284704f1512419d73d65df4 — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS/CONCERNS are advisory.

First-Principles-Verdict: CONCERNS

_REPORT_FIELDS re-spells the fold's own worker-field list and pins it with a test, where a free function-local import of the one authority would do.

Not justified as shipped

  • Item 9 — duplicate of src/kiro_crew/crew_log/projection.py:5053: _REPORT_FIELDS = ("status", "summary", "artifacts", "pr") is a second spelling of projection._WORK_WORKER_FIELDS (count: 2, grep _WORK_WORKER_FIELDS), kept in step only by test_the_report_fields_this_module_digests_are_the_folds. The stamp is computed on the fold worker's thread, where projection is already loaded — the comment this PR deletes from eager.py states the principle: "ONE authority for the type … a second literal here would be a thing to keep in step with the first for no gain, since this runs on the worker thread where an import is free." A prior round already removed the identical duplicate for the fold name (description: "WORK_FOLD duplicate: deleted"), leaving this as 1 unfixed sibling.
    Subtraction: delete _REPORT_FIELDS and its equality test; read the fold's tuple via a function-local import in _report_stamp.
    Clears when: the deletion is made, or a rebuttal names why projection may not be imported there.

What this change ships

Inventory (10 items) — 8 justified

Intent: deliver the already-shipped conductor pull-forward through the crew-log bus instead of a consumer hard-wired into the eager drain — a MOVE of an existing capability (RFC rfc-crew-log-wake.md, in-progress on base, covers the keyed-subscription shape).

  1. A worker's report wakes its conductor via a keyed bus subscription, not a drain hook — justified
  2. The crew-log folder no longer names any conductor (_push_conductor_wakes, fire_for_worker_slot_from_thread removed; 0 remaining callers, grep both names) — justified
  3. Subscriptions live with the service: joined at start and on loop-table changes, disposed on loop end or stop — justified
  4. Which item reported is now a per-item report-stamp diff against the last board seen — justified
  5. The first board seen (the baseline) pushes nothing; the boot tick reads what preceded it — justified
  6. A repeat report identical in every field no longer pushes — justified
  7. A nested conductor's own writes are excluded by unchanged stamps instead of a board-mismatch gate — justified
  8. Two new push-miss windows (no subscriber yet, fold ceiling) fall to the slow tick — justified
  9. A local copy of the fold's worker-field list, pinned equal by a test — duplicate of src/kiro_crew/crew_log/projection.py (_WORK_WORKER_FIELDS)
  10. reset_for_tests() seam aliasing dispose_all — rides along, undeclared; harm-free, matches bus.reset_for_tests

[FIRST-PRINCIPLES-REVIEWED] c279226

Description read

[DESCRIPTION-READ] 3edce8fb6c0f6533e0e78248d38d630259abd2a29297ddcc9f3681102a23c3cc

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of c279226c12c7feadd284704f1512419d73d65df4 and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] c279226

False positive or not applicable? A repository writer can comment:
/ai-review override gpt c279226c12c7feadd284704f1512419d73d65df4: <one-sentence reason>

@github-actions

github-actions Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5 Review — ✅ no blocking findings

Reviewed c279226c12c7feadd284704f1512419d73d65df4 — this comment is updated in place on each push.

Review details

One advisory finding: a baseline-materialised item's first appearance in the board is read as a worker report, so a conductor's own write pulls its own loop forward.

FINDING — src/kiro_crew/conductor_wake.py:158 — previous.get(item_id) != stamp treats an item id absent from the previous board as "reported": a conductor's close/decide/verdict on a legacy item (recorded_at empty) writes a baseline: True entry carrying the committed last_report_at/status/summary/artifacts/pr (dashboard/handlers/work_ledger.py:807), projection._work_step materialises the item with a non-empty last_report_at (projection.py:5261-5275), the item is new to _registry.boards[board], so _report_stamp is non-empty and differs → _fire(svc, board, item_id) spends a pull-forward (and a quiet-streak tick) on the conductor's own bookkeeping — the exact property the deleted expected_board gate held → Fix: in _Registry.observe, do not report an item absent from previous when its rendered item carries baseline True (the fold materialised it from the record, not from a new report), which means passing that flag through _board_items/_Item.

[OPUS-REVIEWED] c279226

Verdict parsed from the review's SHA-scoped output markers for commit c279226c12c7feadd284704f1512419d73d65df4.

False positive or not applicable? A repository writer can comment:
/ai-review override fable c279226c12c7feadd284704f1512419d73d65df4: <one-sentence reason>

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@chenmingwei23
chenmingwei23 force-pushed the feat/conductor-wake-bus-subscriber branch from 57d6d7a to 889cf7d Compare October 2, 2026 07:18
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 2, 2026
@chenmingwei23
chenmingwei23 marked this pull request as draft October 2, 2026 08:31
@chenmingwei23
chenmingwei23 force-pushed the feat/conductor-wake-bus-subscriber branch from 889cf7d to 825cd8d Compare October 2, 2026 16:59
@chenmingwei23 chenmingwei23 changed the title feat(crew-log): make the conductor pull-forward a bus subscriber feat(crew-log): make the conductor pull-forward a keyed bus subscriber Oct 2, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author

Ownership: this PR is driven by session chat-2372 (conductor chat-1875). Head: 825cd8d. Please do not push to this branch.

@chenmingwei23
chenmingwei23 marked this pull request as ready for review October 2, 2026 16:59
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: action required A blocking check or review needs attention labels Oct 2, 2026
@chenmingwei23
chenmingwei23 force-pushed the feat/conductor-wake-bus-subscriber branch from 825cd8d to c2ef33f Compare October 2, 2026 17:26
@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 2, 2026
@chenmingwei23
chenmingwei23 force-pushed the feat/conductor-wake-bus-subscriber branch from c2ef33f to afa9251 Compare October 2, 2026 18:38
@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision labels Oct 2, 2026
@chenmingwei23

chenmingwei23 commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=822a88d1f561 Item 3 - worker map duplicates read_binding

fixed in afa9251: the subtraction is made as written.
_Registry.workers, _release, lookup, the two-claims rule and the sync_subscriptions await in fire_for_worker_slot are deleted.
Close and turn end resolve worker -> (conductor, item) through work_ledger.read_binding again (_read_binding, off the loop), and conductor_wake.py is back on _PERMITTED_STORE_IMPORTERS for that one read.
The registry now holds only each watched board's report stamps, for the bus-side diff.
The RFC's triggers 2 and 3 text is restored to the binding lookup.

@chenmingwei23

chenmingwei23 commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor Author
  • span=fe96c664d8be actionable reports sharing a whole-second stamp skip the second pull-forward

fixed in afa9251: the diffed stamp is last_report_at joined with the item's newest report event id, so each report moves it.
test_two_reports_in_one_second_each_push; reverting to last_report_at alone fails it.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 2, 2026
wave1 verify added 2 commits October 2, 2026 19:15
The crew-log eager drain had a hard-wired second consumer: `_push_conductor_wakes`
imported `conductor_wake`, read the work-ledger binding file for every
`work/recorded` wake, and fired the bound conductor's loop. That put a consumer's
name in the producer and needed a store-import allowlist entry the work ledger had
to argue for.

`crew_log.bus` now publishes every advanced fold as `FoldAdvanced(scope, key,
fold, revision, value, seq)`, and the `work` fold's key is the conductor's own
board, so `conductor_wake` subscribes to that event at `AutoNudgeService.start`
instead. It keeps the last board it saw per key and diffs each item's
`last_report_at`: an item whose stamp moved is a worker that reported and names
the item for the pull-forward cap; a board whose stamps are unchanged moved on a
conductor's own write and pushes nothing, which also keeps a nested conductor's
bookkeeping off its parent's budget. The same registry answers the close and
turn-end triggers in reverse (worker slot -> board, item) from the
`worker_session_key` each item carries; a worker it has not seen primes the
registry once from the `work` fold's read path, bounded by the active loops.

`eager.py` loses the hook and names no conductor; `conductor_wake.py` reads no
store and leaves `_PERMITTED_STORE_IMPORTERS`. The RFC and the crew-log
projection spec describe the subscriber.
One keyed subscription per board an active work-ledger loop watches,
(slot, <board>, work), joined with baseline=True and disposed when the
loop ends or the service stops. The subscriptions follow the AutoNudge
loop table through its observer hook. Replaces the once-per-process
unkeyed subscription and the store-read prime; the fold name comes from
work_vocab instead of a local spelling.
@chenmingwei23
chenmingwei23 force-pushed the feat/conductor-wake-bus-subscriber branch from afa9251 to c279226 Compare October 2, 2026 19:18
@chenmingwei23

Copy link
Copy Markdown
Contributor Author
  • span=2c13fef538ab Item 8 - sync_subscriptions returned join tasks no caller awaited

fixed in c279226: the subtraction is made as written.
sync_subscriptions returns nothing and its docstring no longer names a consumer; the join tasks live only in _subscriptions.joining, which the tests read.

@chenmingwei23

Copy link
Copy Markdown
Contributor Author
  • span=fe96c664d8be same-second reports reuse the content-addressed event id, so changed artifacts or pr leave the stamp unchanged

fixed in c279226: the stamp is last_report_at plus a digest of every field a report writes (status, summary, artifacts, pr) and the newest report event id.
test_a_same_second_report_with_the_same_event_id_still_pushes_on_new_fields; digesting the event id alone fails it. The field list is pinned to the fold's own _WORK_WORKER_FIELDS.

@github-actions github-actions Bot added readiness: checking Automated validation is still running and removed readiness: passed Eligible automated validation passed for the current revision labels Oct 2, 2026
@chenmingwei23

Copy link
Copy Markdown
Contributor Author
  • span=e85312139d17 Item 9 - _REPORT_FIELDS respells projection._WORK_WORKER_FIELDS

rebutted: projection may not be imported by conductor_wake at module level.
conductor_wake is imported by AutoNudgeService.start on the gateway's boot path, and the crew log states the fold surface must stay off it (crew_log/bus.py:278, crew_log/eager.py:213 and :662 keep every projection import function-local for that reason).
_WORK_WORKER_FIELDS is also a private name of projection; there is no public leaf for it, unlike work_vocab.WORK_FOLD_NAME, which this PR now imports instead of respelling.
The pin test test_the_report_fields_this_module_digests_are_the_folds fails the build the moment the two diverge, which is the repo's pattern for a boot-path-local spelling.

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: checking Automated validation is still running labels Oct 2, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving at c279226c12. CI at this head: 82 success, 12 skipped, 0 failing. I did not run the suite locally.

Verified against source

  • Every _emit call site in the loop table runs inside an async method, and the one sync function (remove_sync) is only reached from async callers, so the Design lane's worry that emits can happen off the service loop does not apply.

Non-blocking follow-ups

  1. One-time spurious pull-forward per pre-existing item. When the conductor first runs close/decide on an item that existed before the projection, it writes a baseline: True row that carries last_report_at (dashboard/handlers/work_ledger.py ~L838 -> projection.py ~L5261). The item looks new to the registry and its stamp is non-empty, so _fire spends one pull-forward. Opus's suggested fix (never fire for baseline-materialized items) would also swallow a worker's real first report on an old item, because that report takes the same baseline path. A narrower condition: fire for a newly seen item only when its event tail has kind == "report". This costs at most one extra pull-forward per old item, so it does not gate this PR.
  2. _REPORT_FIELDS duplicates projection._WORK_WORKER_FIELDS (both ("status","summary","artifacts","pr")), and only a test keeps them in sync. Importing the single definition inside the function would remove the drift risk.

@chenmingwei23
chenmingwei23 merged commit 6ce8c4b into main Oct 3, 2026
97 checks passed
@chenmingwei23
chenmingwei23 deleted the feat/conductor-wake-bus-subscriber branch October 3, 2026 05:11
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Oct 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants