Committee aggregation #282

kamilsa · 2026-01-14T12:38:27Z

🗒️ Description

Introduces aggregator role and subnet aggregation.

Every validator is assigned to one of the attestation subnets
Aggregators collect signatures that correspond to validators from their subnet
* If aggregators collected 90% of signatures from their subnet by the beginning of slot 2, they produce aggregated attestation and propagate it into aggregation topic
Validators subscribe to aggregation topic, so that next block proposer may include committee aggregations into the block (without recursive aggregation for now)

Interval	Devnet 2	Devnet 3
0	Aggregate signatures and put proofs into the block	Put collected subnet proofs into the block
1	Cast a vote and publish to attestation topic	Cast a vote and publish to attestation topic + publish to attestation_{subnet_id} topic
2	Update safe target	Update safe target. Aggregator: aggregate collected signatures and broadcast a subnet proof into the aggregation topic
3	Attestations accepted	Attestations accepted

Remaining work

~~- [ ] Process the case when aggregators did not observe enough signatures by the beginning of interval 2~~
- [ ] Add predicates for gossipsub propagations of aggregated signatures (e.g. do not propagate aggregation if we already observed the one for the same committee, but proving more validators signatures) Not needed for now as we have only a single aggregator per committee, so only one aggregation

Update to latest master

🔗 Related Issues or PRs

leanEthereum/pm#56
leanEthereum/pm#58

✅ Checklist

Ran tox checks to avoid unnecessary CI fails:
```
uvx tox
```
Considered adding appropriate tests for the changes (will add in a separate PR)
Considered updating the online docs in the ./docs/ directory.

use committee aggregated signature proofs

also rename gossip_signatures to gossip_committee_signatures

jihoonsong

Great work! Please excuse leaving some comments while it's still in draft. Just wanted to help iterate faster :)

docs/client/validator.md

jihoonsong · 2026-01-14T15:25:40Z

src/lean_spec/subspecs/containers/state/state.py

        # Configure the genesis state.
        genesis_config = Config(
            genesis_time=genesis_time,
+            attestation_subnet_count=AGGREGATION_COMMITTEE_COUNT,


I admit that I was the one who advocated for attestation committee, but based on the fact that validators only push their attestations to aggregators in their subnet without subscribing to it, I now think aggregation committee gives us slightly better description.

I don't mind whichever we choose—either attestation committee or aggregation committee—but I do think we need to stick to one thing consistently in the Lean spec and pq-devnet-3.md in the pm repo.

I don't have a strong preference too, however I think the rationale for topic names in beacon chain spec is based on the type of messages that are being propagated to this topic. For consistency we should probably stick to the same logic and keep using attestation subnets and attestation committees

Sounds great! In the same vein, what do you think about this one?

looks good to me, applied your suggestion

src/lean_spec/subspecs/forkchoice/store.py

…ted references

# Conflicts: # src/lean_spec/subspecs/forkchoice/store.py # src/lean_spec/subspecs/networking/__init__.py

src/lean_spec/subspecs/networking/gossipsub/topic.py

docs/client/validator.md

jihoonsong · 2026-01-15T11:42:53Z

docs/client/validator.md

-
-When aggregation is added, aggregators will collect attestations and combine them.
-Aggregated attestations will be broadcast separately.
+Devnet-2 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.


Suggested change

Devnet-2 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.

Devnet-3 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.

…nt in configuration

Aggregate during interval 2 if more threshold signatures were received

g11tech · 2026-01-21T09:45:54Z

docs/client/validator.md

+
+In the devnet-3 design, however, there is one global subnet for signed 
+attestations propagation, in addition to publishing into per committee subnets.
+This is due to 3SF-mini consensus design, that requires 2/3+ of all 


this global bit is not required, once the aggregtors publish signed attestations in the 2nd interval, they can be imported by all validators in the 3rd interval

Unfortunately, without global topic for attestations, we might not be able to receive proofs in time to update safe target during interval 2:

Interval 0: block propagation

Interval 1: votes propagation

Interval 2: signatures aggregation (up to one second for 1000 validators in subnet with 1000sigs/second expected sigs aggregation rate) + proof distribution => No time for updating safe target => in next slot validator votes for old target

src/lean_spec/subspecs/chain/config.py

g11tech · 2026-01-21T10:20:53Z

src/lean_spec/subspecs/containers/attestation/attestation.py

            for data, validator_ids in data_to_validator_ids.items()
        ]
+
+class SignedAggregatedAttestation(Container):


@anshalshukla / @GrapeBaBa do we already have this type?

also better to use message, signature terminlogy

I think we also need aggregated bit vector here as well,

I think we also need aggregated bit vector here as well,

AggregatedSignatureProof contains AggregationBits

@anshalshukla / @GrapeBaBa do we already have this type?

no

This reverts commit 3115ef5.

This reverts commit 9174f5b.

…ttee_count in configuration" This reverts commit 3477d6e.

This reverts commit 6556e81.

GrapeBaBa · 2026-01-27T03:38:49Z

docs/client/networking.md

+
+| Topic Name                                                 | Message Type                | Encoding     |
+|------------------------------------------------------------|-----------------------------|--------------|
+| /lean/consensus/devnet3/blocks/ssz_snappy                  | SignedBlockWithAttestation  | SSZ + Snappy |


original prefix is /leanconsensus, this is an expected change /lean/consensus?

no.
Thanks for noticing. Fixed

# Conflicts: # src/lean_spec/subspecs/chain/config.py # src/lean_spec/subspecs/containers/state/state.py

Copilot

Pull request overview

Introduces committee-level attestation aggregation and subnet-aware validator behavior, updating forkchoice, networking, and node layers to support an aggregator role and per-validator store context in preparation for devnet-3.

Changes:

Extend the forkchoice Store and State to track a local validator_id, manage per-attester XMSS signatures and aggregated proofs, and use SignedAggregatedAttestation/aggregated_payloads for block production and attestation processing.
Add subnet and topic abstractions for per-committee attestation gossip and aggregation (compute_subnet_id, new gossipsub topic kinds) and wire validator-aware stores into Node, SyncService, and networking.
Update tests, fixtures, and documentation to reflect the new aggregation model, Store.get_forkchoice_store API, and gossip decoding behavior.

Reviewed changes

Copilot reviewed 32 out of 32 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tests/lean_spec/subspecs/validator/test_service.py	Adjusts validator service tests to use a test `validator_id` and the new `Store.get_forkchoice_store` signature; updates attestation tests to work with aggregated payloads instead of raw gossip signatures.
tests/lean_spec/subspecs/ssz/test_state.py	Updates the SSZ encoding round-trip test to a single-line expected hex string consistent with current `State` encoding.
tests/lean_spec/subspecs/node/test_node.py	Updates node tests to pass `validator_id` into `Node._try_load_from_database`, validating that store time still uses intervals per slot.
tests/lean_spec/subspecs/networking/test_network_service.py	Extends the mock networking store with a `validator_id` and `on_gossip_attestation` signature compatible with the aggregator-aware `SyncService`.
tests/lean_spec/subspecs/networking/client/test_gossip_reception.py	Allows `decode_message` to return `None` in type hints and asserts non-`None` for valid block/attestation topics.
tests/lean_spec/subspecs/forkchoice/test_validator.py	Ensures all forkchoice validator tests construct `Store` with a `validator_id`, exercising block production and attestation with the updated store API.
tests/lean_spec/subspecs/forkchoice/test_time_management.py	Adds `validator_id` to stores and updates `get_forkchoice_store` usage and time-based tests to the new parameter names.
tests/lean_spec/subspecs/forkchoice/test_store_attestations.py	Switches attestation storage tests from `gossip_signatures` to explicit aggregated proofs and `aggregated_payloads`, including immutability checks with the new API.
tests/lean_spec/subspecs/containers/test_state_aggregation.py	Rewrites block-building aggregation tests to use aggregated proofs only (`aggregated_payloads`) and the new gossip-aggregation separation, dropping direct `gossip_signatures` usage.
tests/lean_spec/helpers/init.py	Introduces `TEST_VALIDATOR_ID` and exports it for consistent test construction of validator-aware stores.
tests/lean_spec/conftest.py	Updates the shared `base_store` fixture to use `Store.get_forkchoice_store` with an explicit `ValidatorIndex` as `validator_id`.
src/lean_spec/subspecs/sync/service.py	Refactors imports for `Store`, `PeerId`, and `SignedAttestation` and routes gossip attestations through `Store.on_gossip_attestation` with an `is_aggregator` flag derived from the store’s `validator_id`.
src/lean_spec/subspecs/node/node.py	Adds `get_local_validator_id`, threads `validator_id` into `Store.get_forkchoice_store` and `_try_load_from_database`, and ensures nodes construct validator-aware stores from genesis or checkpoint.
src/lean_spec/subspecs/node/helpers.py	Introduces an `is_aggregator(validator_id)` helper (currently a placeholder that always returns `False`) for future ENR-based aggregator selection.
src/lean_spec/subspecs/node/init.py	Re-exports `get_local_validator_id` alongside `Node` and `NodeConfig`.
src/lean_spec/subspecs/networking/subnet.py	Adds `compute_subnet_id` to map validator indices to attestation subnet IDs based on committee count.
src/lean_spec/subspecs/networking/service/service.py	Updates gossip attestation handling to call the new `SyncService.on_gossip_attestation` signature using keyword arguments.
src/lean_spec/subspecs/networking/gossipsub/topic.py	Defines `ATTESTATION_SUBNET` and `AGGREGATED_ATTESTATION` topic kinds and a `committee_aggregation` factory, extending the topic system for subnet and aggregation channels.
src/lean_spec/subspecs/networking/client/event_source.py	Changes `GossipHandler.decode_message` to return `Optional` and adjusts tests/callers, while still only decoding block and global attestation topics.
src/lean_spec/subspecs/networking/init.py	Re-exports `compute_subnet_id` from the networking package for use by forkchoice and other subspecs.
src/lean_spec/subspecs/forkchoice/store.py	Extends `Store` with `validator_id`, updates `get_forkchoice_store`, rewires attestation handling to distinguish gossip vs aggregated proofs, adds `on_gossip_aggregated_attestation`, committee signature aggregation, and aggregator-aware ticking, and changes block processing to conditionally cache proposer signatures by committee.
src/lean_spec/subspecs/containers/state/state.py	Splits signature aggregation into gossip aggregation vs selection from `aggregated_payloads`, updates `build_block` to rely solely on aggregated proofs, and adds helper methods for reusing/combining proofs.
src/lean_spec/subspecs/containers/attestation/attestation.py	Imports aggregation types and introduces `SignedAggregatedAttestation` to carry attestation data plus an aggregated signature proof.
src/lean_spec/subspecs/containers/attestation/init.py	Exports `SignedAggregatedAttestation` from the attestation package.
src/lean_spec/subspecs/containers/init.py	Re-exports `SignedAggregatedAttestation` at the top-level containers namespace.
src/lean_spec/subspecs/chain/config.py	Adds `ATTESTATION_COMMITTEE_COUNT` configuration constant (currently set to `1`) for committee/subnet computations.
src/lean_spec/main.py	Threads `validator_id` into `Store.get_forkchoice_store` when initializing from checkpoint and imports `get_local_validator_id` from the node package.
packages/testing/src/consensus_testing/test_fixtures/verify_signatures.py	Simplifies block-fixture building by dropping direct `gossip_signatures` input to `State.build_block` in favor of empty `aggregated_payloads`.
packages/testing/src/consensus_testing/test_fixtures/state_transition.py	Removes ad-hoc gossip signature generation from fixture-based state transitions, aligning with the new block-building API.
packages/testing/src/consensus_testing/test_fixtures/fork_choice.py	Adapts fixture-based fork choice tests to validator-aware stores, passes `current_validator` into `on_block`, and uses the new committee aggregation APIs to build aggregated payloads before calling `State.build_block`.
docs/client/validator.md	Updates validator docs to describe committees, attestation subnets, aggregator role, and the new attestation/aggregation flow for devnet-3.
docs/client/networking.md	Expands networking docs with committee assignment metadata, detailed gossip topics (including subnet and aggregation topics), and the corresponding SSZ message types.

Comments suppressed due to low confidence (1)

src/lean_spec/subspecs/networking/client/event_source.py:388

GossipHandler.decode_message only handles TopicKind.BLOCK and TopicKind.ATTESTATION, but now that TopicKind also includes ATTESTATION_SUBNET and AGGREGATED_ATTESTATION the function silently falls through and returns None for those topics. Together with _handle_gossip_message only matching on BLOCK/ATTESTATION, this means subnet and aggregation topics described in the updated networking docs are effectively ignored rather than yielding SignedAttestation/SignedAggregatedAttestation or a clear error. It would be more robust either to add explicit branches for the new topic kinds (decoding to the expected SSZ types) or to raise a GossipMessageError for unsupported kinds, and to update the docstring to reflect the | None return behavior if you keep the None path.

    def decode_message(
        self,
        topic_str: str,
        compressed_data: bytes,
    ) -> SignedBlockWithAttestation | SignedAttestation | None:
        """
        Decode a gossip message from topic and compressed data.

        Processing proceeds in order:

        1. Parse topic to determine message type.
        2. Decompress Snappy-framed data.
        3. Decode SSZ bytes using the appropriate schema.

        Each step can fail independently. Failures are wrapped in
        GossipMessageError for uniform handling.

        Args:
            topic_str: Full topic string (e.g., "/leanconsensus/0x.../block/ssz_snappy").
            compressed_data: Snappy-compressed SSZ data.

        Returns:
            Decoded block or attestation.

        Raises:
            GossipMessageError: If the message cannot be decoded.
        """
        # Step 1: Parse topic to determine message type.
        #
        # The topic string contains the fork digest and message kind.
        # Invalid topics are rejected before any decompression work.
        # This prevents wasting CPU on malformed messages.
        try:
            topic = GossipTopic.from_string(topic_str)
        except ValueError as e:
            raise GossipMessageError(f"Invalid topic: {e}") from e

        # Step 2: Decompress Snappy-framed data.
        #
        # Gossipsub uses raw Snappy compression (not framed).
        #
        # Raw Snappy has no stream identifier or CRC checksums.
        # Decompression fails if:
        #   - Compressed data is corrupted or truncated.
        #   - Copy offsets reference data beyond buffer bounds.
        #
        # Failed decompression indicates network corruption or a malicious peer.
        try:
            ssz_bytes = decompress(compressed_data)
        except SnappyDecompressionError as e:
            raise GossipMessageError(f"Snappy decompression failed: {e}") from e

        # Step 3: Decode SSZ based on topic kind.
        #
        # SSZ decoding fails if the bytes don't match the expected schema.
        # For example: wrong length, invalid field values, or truncation.
        #
        # The topic determines which schema to use. This is why topic
        # validation must happen first.
        try:
            match topic.kind:
                case TopicKind.BLOCK:
                    return SignedBlockWithAttestation.decode_bytes(ssz_bytes)
                case TopicKind.ATTESTATION:
                    return SignedAttestation.decode_bytes(ssz_bytes)
        except SSZSerializationError as e:

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-01-28T09:57:00Z

src/lean_spec/subspecs/node/helpers.py

+    return (
+        False  # Placeholder implementation, in future should be defined by node operator settings
+    )


is_aggregator is currently hard-coded to always return False, while the validator/networking docs now describe aggregators being selected via an is_aggregator ENR flag. As a result, the runtime node never enters the aggregator code paths in Store.on_gossip_attestation/tick_interval (collection of committee signatures and aggregation), which could be confusing given the documentation. If this placeholder behavior is intentional for devnet-3, consider adding an explicit TODO or brief comment tying this helper to the future ENR-based configuration so that the divergence from the docs is clear.

Suggested change

return (

False # Placeholder implementation, in future should be defined by node operator settings

)

# TODO(devnet-3): This is a placeholder. Once ENR-based configuration is wired in,

# this helper should consult the validator's ENR `is_aggregator` flag (or equivalent

# node-operator setting) instead of always returning False.

return False

Copilot · 2026-01-28T09:57:00Z

src/lean_spec/subspecs/forkchoice/store.py

+        new_aggregated_payloads = dict(self.aggregated_payloads)
+
+        attestations = self.latest_new_attestations
+        committee_signatures = self.gossip_signatures
+
+        attestation_list = [
+            Attestation(validator_id=vid, data=data) for vid, data in attestations.items()
+        ]
+
+        head_state = self.states[self.head]
+        # Perform aggregation
+        aggregated_results = head_state.aggregate_gossip_signatures(
+            attestation_list,
+            committee_signatures,
+        )
+
+        # iterate to broadcast aggregated attestations
+        for aggregated_attestation, aggregated_signature in aggregated_results:
+            _ = SignedAggregatedAttestation(
+                data=aggregated_attestation.data,
+                proof=aggregated_signature,
+            )
+            # Note: here we should broadcast the aggregated signature to committee_aggregators topic
+
+        # Compute new aggregated payloads
+        for aggregated_attestation, aggregated_signature in aggregated_results:
+            data_root = aggregated_attestation.data.data_root_bytes()
+            validator_ids = aggregated_signature.participants.to_validator_indices()
+            for vid in validator_ids:
+                sig_key = SignatureKey(vid, data_root)
+                if sig_key not in new_aggregated_payloads:
+                    new_aggregated_payloads[sig_key] = []
+                new_aggregated_payloads[sig_key].append(aggregated_signature)


aggregate_committee_signatures builds new_aggregated_payloads via a shallow dict(self.aggregated_payloads) copy and then appends to the inner lists, which means previous Store snapshots can observe mutations to their aggregated_payloads lists. Other code paths (e.g. on_gossip_aggregated_attestation) deep-copy the map to preserve Store immutability, so this shallow copy is inconsistent with that pattern and risks subtle bugs when older Store instances are reused in tests or logic. Consider deep-copying the values (or using copy.deepcopy) before mutating so that each Store instance has its own independent aggregated_payloads structure.

unnawut · 2026-01-29T08:01:39Z

src/lean_spec/subspecs/containers/state/state.py

+
+        return results
+
+    def compute_aggregated_signatures(


We should remove this compute_aggregated_signatures() function since it's only serving the spec's unit tests. I can have a go at this after the PR is merged, but just flagging that clients don't need to implement this function.

unnawut · 2026-01-29T08:13:57Z

src/lean_spec/subspecs/forkchoice/store.py


-        # Return store with updated signature map
-        return store.model_copy(update={"gossip_signatures": new_gossip_sigs})
+        # Return store with updated signature maps


super nit: it's still a single map

Suggested change

# Return store with updated signature maps

# Return store with updated signature map

unnawut · 2026-01-29T08:26:44Z

src/lean_spec/subspecs/forkchoice/store.py

    def on_block(
        self,
        signed_block_with_attestation: SignedBlockWithAttestation,
+        current_validator: ValidatorIndex | None = None,


Should this use the internal self.validator_id similar to on_gossip_attestation() above instead of allowing a custom arg?

kamilsa added 14 commits January 13, 2026 09:47

networking: update committee docs

b5b6d8a

networking: add committee size configuration

4867d7d

store committee attestations

7bcedca

Add aggregation in 2nd interval

980b5e8

Committee aggregation

60468af

Rename aggregation committee size to count for clarity

213504a

Remove committee signatures

4fac983

Refactor build_block:

f2651d8

use committee aggregated signature proofs

Clarify attestation broadcasting and update Devnet reference

cc7548c

remove adding proposer signatures to gossip_signatures

cb1a21b

also rename gossip_signatures to gossip_committee_signatures

Refactor subnet ID computation and rename committee signatures variable

e398823

Store proposer signature if same subnet

90fc114

Update build block with selecting aggregations

cdae6a4

Uncomment on_attestation during on_gossip_aggregation

b24d3ed

kamilsa mentioned this pull request Jan 14, 2026

PQ Interop #22 | Jan 14, 2026 ethereum/pm#1866

Closed

Update gossipsub topic names to reflect devnet3

5c952ff

jihoonsong reviewed Jan 14, 2026

View reviewed changes

kamilsa added 2 commits January 15, 2026 16:13

Rename aggregation committee to attestation committee and update rela…

8a0c121

…ted references

Merge remote-tracking branch 'origin/main' into committee-aggregation

cb952f8

# Conflicts: # src/lean_spec/subspecs/forkchoice/store.py # src/lean_spec/subspecs/networking/__init__.py

jihoonsong reviewed Jan 15, 2026

View reviewed changes

kamilsa added 6 commits January 15, 2026 19:59

refactor: rename committee aggregation topic to aggregated attestation

9d721bd

update validator.md to clarify subnet usage in attestation committees

baddbeb

feat: add threshold ratio for committee signature aggregation

6556e81

feat: replace attestation_subnet_count with attestation_committee_cou…

3477d6e

…nt in configuration

feat: add committee signature threshold ratio chain config

9174f5b

feat: aggregate on gossip

3115ef5

Aggregate during interval 2 if more threshold signatures were received

g11tech reviewed Jan 21, 2026

View reviewed changes

src/lean_spec/subspecs/chain/config.py Outdated Show resolved Hide resolved

g11tech reviewed Jan 21, 2026

View reviewed changes

docs: clarify aggregator role in validator participation

3fffe71

unnawut added the specs Scope: Changes to the specifications label Jan 23, 2026

unnawut added this to the pq-devnet-3 milestone Jan 23, 2026

kamilsa added 4 commits January 23, 2026 10:36

Revert "feat: aggregate on gossip"

d0462aa

This reverts commit 3115ef5.

Revert "feat: add committee signature threshold ratio chain config"

e2fd644

This reverts commit 9174f5b.

Revert "feat: replace attestation_subnet_count with attestation_commi…

d40199c

…ttee_count in configuration" This reverts commit 3477d6e.

Revert "feat: add threshold ratio for committee signature aggregation"

d46dd08

This reverts commit 6556e81.

GrapeBaBa reviewed Jan 27, 2026

View reviewed changes

kamilsa added 13 commits January 27, 2026 10:49

Merge remote-tracking branch 'origin/main' into committee-aggregation

2439177

# Conflicts: # src/lean_spec/subspecs/chain/config.py # src/lean_spec/subspecs/containers/state/state.py

refactor: update current_validator_id type from Uint64 to ValidatorIndex

61b8100

Fix tests

d66dfd3

refactor: remove attestation_subnet_count from configuration

360bfb0

Fix tests after attestation_subnet_count from Config

379ddd6

Add validator_id to store & fix tests

fe8317c

rrely on aggregated payloads for block production

6af933b

Fix uvx tox

2b68c0c

Small fixes

22bd960

Fix ci: refactor attestation handling for block construction

7cf9773

Fix ci

6e85356

Fix ci

da21184

Refactor attestation handling to support committee signature aggregation

6ad7b19

kamilsa changed the title ~~[WIP] Committee aggregation~~ Committee aggregation Jan 28, 2026

kamilsa marked this pull request as ready for review January 28, 2026 09:44

Copilot AI review requested due to automatic review settings January 28, 2026 09:44

Copilot started reviewing on behalf of kamilsa January 28, 2026 09:44 View session

Copilot AI reviewed Jan 28, 2026

View reviewed changes

unnawut reviewed Jan 29, 2026

View reviewed changes

	Devnet-2 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.
	Devnet-3 introduces signatures aggregation. Aggregators will collect attestations and combine them. Aggregated attestations will be broadcast separately.

-    return (
-        False  # Placeholder implementation, in future should be defined by node operator settings
-    )
+    # TODO(devnet-3): This is a placeholder. Once ENR-based configuration is wired in,
+    # this helper should consult the validator's ENR `is_aggregator` flag (or equivalent
+    # node-operator setting) instead of always returning False.
+    return False

	# Return store with updated signature maps
	# Return store with updated signature map

Committee aggregation #282

Are you sure you want to change the base?

Committee aggregation #282

Conversation

kamilsa commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🗒️ Description

Remaining work

🔗 Related Issues or PRs

✅ Checklist

Uh oh!

jihoonsong left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

g11tech Jan 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Jan 28, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

kamilsa commented Jan 14, 2026 •

edited

Loading

g11tech Jan 21, 2026 •

edited

Loading