Implement minimal client/server game prototype with Spring Boot backend and LWJGL frontend by Copilot · Pull Request #1 · Preponderous-Software/barony

Copilot · 2026-02-08T16:59:04Z

Original prompt

Generate a minimal, runnable client/server prototype.

Backend: Java Spring Boot, REST, in-memory. Owns all game logic.
Include:

2D grid

TileType: CASTLE, VILLAGE, EMPTY

Villages generate soldiers per tick

Army movement and integer-based combat
Endpoints: GET /state, POST /tick, POST /command

Frontend: Java LWJGL.
Render grid with simple shapes, show tiles/armies, send one command via HTTP.

Constraints: Separate projects. No DB, auth, AI, assets, or polish.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot

Pull request overview

Adds a minimal end-to-end runnable prototype consisting of a Spring Boot backend that owns game state/mechanics and an LWJGL frontend that renders the grid and issues commands via REST.

Changes:

Introduces Spring Boot REST server with in-memory grid, armies, tick progression (village growth), and combat resolution.
Adds LWJGL client that renders the grid/armies and calls /state, /tick, and /command over HTTP.
Adds helper scripts (start-*.sh, demo-api.sh), plus README/.gitignore for running the prototype.

Reviewed changes

Copilot reviewed 22 out of 23 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
start-frontend.sh	Script to build/run the LWJGL client via Maven exec plugin
start-backend.sh	Script to run the Spring Boot server via Maven
demo-api.sh	Curl-based demo of state/tick/command API
README.md	Documents rules, endpoints, and run instructions
.gitignore	Ignores Maven/IDE/OS artifacts
backend/pom.xml	Spring Boot web backend project definition
backend/src/main/java/com/barony/backend/BackendApplication.java	Backend entry point
backend/src/main/java/com/barony/backend/controller/GameController.java	REST endpoints for state/tick/command
backend/src/main/java/com/barony/backend/service/GameService.java	Core game state + tick/command/combat logic
backend/src/main/java/com/barony/backend/model/*	Backend models for tiles, armies, commands, state
backend/src/main/resources/application.properties	Configures server port (8080)
frontend/pom.xml	LWJGL + Gson frontend project definition
frontend/src/main/java/com/barony/frontend/FrontendApplication.java	LWJGL window loop + simple input-to-API wiring
frontend/src/main/java/com/barony/frontend/client/GameClient.java	Simple HttpURLConnection REST client
frontend/src/main/java/com/barony/frontend/model/*	Frontend DTOs for JSON deserialization

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

Copilot · 2026-02-08T17:53:11Z

+    public GameState getState() {
+        try {
+            URL url = new URL(baseUrl + "/state");
+            HttpURLConnection conn = (HttpURLConnection) url.openConnection();
+            conn.setRequestMethod("GET");
+
+            StringBuilder response = new StringBuilder();
+            try (BufferedReader in = new BufferedReader(new InputStreamReader(conn.getInputStream()))) {
+                String line;


HttpURLConnection is never disconnected and no connect/read timeouts are set. This can leak sockets and hang the render thread indefinitely if the backend is down or slow. Add reasonable timeouts and ensure conn.disconnect() is called in a finally block; also handle non-2xx responses via getErrorStream().

Added connection timeout (5s), read timeout (10s), proper disconnect() in finally blocks, and error stream handling for non-2xx responses. Commit: 66c55d0

Copilot · 2026-02-08T17:53:11Z

+            conn.setRequestProperty("Content-Type", "application/json");
+            conn.setDoOutput(true);
+
+            String jsonCommand = gson.toJson(command);
+            try (OutputStream os = conn.getOutputStream()) {
+                os.write(jsonCommand.getBytes());
+                os.flush();


jsonCommand.getBytes() uses the platform default charset, which can produce invalid JSON on non-UTF-8 platforms. Encode explicitly as UTF-8 (and ideally set the request charset in the Content-Type header).

Changed to explicit UTF-8 encoding using StandardCharsets.UTF_8 and added charset to Content-Type header. Commit: 66c55d0

Copilot · 2026-02-08T17:53:11Z

+        <dependency>
+            <groupId>org.lwjgl</groupId>
+            <artifactId>lwjgl</artifactId>
+            <classifier>natives-linux</classifier>
+        </dependency>
+        <dependency>
+            <groupId>org.lwjgl</groupId>
+            <artifactId>lwjgl-glfw</artifactId>
+            <classifier>natives-linux</classifier>
+        </dependency>
+        <dependency>
+            <groupId>org.lwjgl</groupId>
+            <artifactId>lwjgl-opengl</artifactId>
+            <classifier>natives-linux</classifier>
+        </dependency>


The LWJGL dependencies hardcode natives-linux classifiers, so the frontend won’t run on macOS/Windows. Consider using OS detection (e.g., os-maven-plugin + a ${lwjgl.natives} property) or Maven profiles to select the correct natives per platform.

Added Maven profiles for automatic platform detection (Linux, macOS Intel/ARM, Windows) using ${lwjgl.natives} property. Commit: 66c55d0

Copilot · 2026-02-08T17:53:11Z

+public class GameService {
+    private GameState gameState;
+
+    public GameService() {
+        initializeGame();
+    }
+
+    private void initializeGame() {
+        gameState = new GameState(10, 10);
+
+        // Set up initial board
+        gameState.getGrid()[0][0].setType(TileType.CASTLE);
+        gameState.getGrid()[9][9].setType(TileType.CASTLE);
+        gameState.getGrid()[3][3].setType(TileType.VILLAGE);
+        gameState.getGrid()[6][6].setType(TileType.VILLAGE);
+
+        // Add initial armies
+        gameState.getArmies().add(new Army(0, 0, 10, 1));
+        gameState.getArmies().add(new Army(9, 9, 10, 2));
+    }
+
+    public GameState getState() {
+        return gameState;
+    }
+
+    public void tick() {
+        gameState.incrementTick();


GameService stores all mutable game state in a singleton Spring @service without any synchronization. Since controller requests can run concurrently, simultaneous /tick and /command calls can race (e.g., inconsistent combat results, ConcurrentModification during serialization, lost updates). Consider guarding all state mutations/reads with a lock (e.g., synchronized methods or a ReentrantLock) and/or returning an immutable snapshot DTO rather than the live GameState object.

Added synchronized keyword to all GameService public methods to prevent race conditions. Also changed getArmies() to return defensive copy. Commits: 66c55d0, 18100a8

Copilot · 2026-02-08T17:53:12Z

+            int armyIndex = command.getArmyIndex();
+            if (armyIndex >= 0 && armyIndex < gameState.getArmies().size()) {
+                Army army = gameState.getArmies().get(armyIndex);
+                int targetX = command.getTargetX();
+                int targetY = command.getTargetY();
+
+                // Validate target position
+                if (targetX >= 0 && targetX < gameState.getWidth() && 
+                    targetY >= 0 && targetY < gameState.getHeight()) {
+                    army.setX(targetX);
+                    army.setY(targetY);


Using "armyIndex" to identify an army is unstable because list ordering can change after combat removals (or future sorting), causing commands to apply to the wrong army. Prefer a stable identifier on Army (e.g., armyId UUID/int) and have Command reference that id instead of list index.

Suggested change

int armyIndex = command.getArmyIndex();

if (armyIndex >= 0 && armyIndex < gameState.getArmies().size()) {

Army army = gameState.getArmies().get(armyIndex);

int targetX = command.getTargetX();

int targetY = command.getTargetY();

// Validate target position

if (targetX >= 0 && targetX < gameState.getWidth() &&

targetY >= 0 && targetY < gameState.getHeight()) {

army.setX(targetX);

army.setY(targetY);

// Use a stable army identifier instead of treating the value as a list index.

int armyId = command.getArmyIndex();

Army targetArmy = null;

for (Army army : gameState.getArmies()) {

// Assuming Army exposes a stable identifier via getId()

if (army.getId() == armyId) {

targetArmy = army;

break;

}

}

if (targetArmy != null) {

int targetX = command.getTargetX();

int targetY = command.getTargetY();

// Validate target position

if (targetX >= 0 && targetX < gameState.getWidth() &&

targetY >= 0 && targetY < gameState.getHeight()) {

targetArmy.setX(targetX);

targetArmy.setY(targetY);

Implemented stable Army ID using AtomicInteger for thread-safe generation. Renamed Command field from armyIndex to armyId for clarity. Updated all code and documentation. Commits: 66c55d0, 18100a8

Copilot · 2026-02-08T17:53:12Z

+import org.springframework.web.bind.annotation.*;
+
+@RestController
+@CrossOrigin(origins = "*")


@crossorigin(origins = "*") enables any website to issue commands to this server from a browser context. Even for a prototype, it’s safer to restrict this to the expected dev origin(s) (e.g., http://localhost:3000 / file:// is not covered) or make it configurable via properties.

Suggested change

@CrossOrigin(origins = "*")

@CrossOrigin(origins = {"http://localhost:3000", "http://127.0.0.1:3000"})

Restricted CORS to localhost origins only (ports 8080 and 3000) instead of wildcard "*". Commit: 66c55d0

Copilot · 2026-02-08T17:53:12Z

+    }
+
+    public List<Army> getArmies() {
+        return armies;


getArmies exposes the internal representation stored in field armies. The value may be modified after this call to getArmies.
getArmies exposes the internal representation stored in field armies. The value may be modified after this call to getArmies.

Suggested change

return armies;

return new ArrayList<>(armies);

Changed getArmies() to return defensive copy (new ArrayList<>(armies)). Added getArmiesInternal() for internal service modifications. Commit: 66c55d0

dmccoystephenson · 2026-02-08T18:04:20Z

@copilot address comments

…port, thread safety, stable army IDs, and CORS restrictions Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

…EADME duplicates Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

dmccoystephenson · 2026-02-08T18:18:03Z

@copilot add CI checks to ensure that the frontend and backend build and that their unit tests pass; this should run on pull requests into main/develop

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot · 2026-02-08T18:21:42Z

@copilot add CI checks to ensure that the frontend and backend build and that their unit tests pass; this should run on pull requests into main/develop

Added GitHub Actions CI workflow that runs on PRs to main/develop branches. The workflow includes:

Backend job:

Builds backend with Maven
Runs 8 unit tests (BackendApplicationTests, ArmyTest, GameStateTest)
Packages the application

Frontend job:

Builds frontend with Maven
Runs 4 unit tests (ArmyTest, CommandTest)
Packages the application

Both jobs use JDK 17 with Temurin distribution and Maven caching. Added JUnit 5 test dependencies and created smoke tests for core models. All tests passing. Commit: 5de53c7

dmccoystephenson · 2026-02-08T18:29:28Z

@copilot currently there seems to be support for two players but for now this is going to be a single player where enemy Lords will be AI

Copilot · 2026-02-08T18:30:27Z

@copilot currently there seems to be support for two players but for now this is going to be a single player where enemy Lords will be AI

Understood. The current implementation uses playerId 1 for the human player and playerId 2 for enemy forces. This structure supports the single-player + AI design - player 1 armies can be controlled via REST commands, while player 2 armies can be controlled by AI logic added to the tick() method in a future update. The existing player distinction will work well for differentiating human vs AI-controlled armies.

dmccoystephenson · 2026-02-08T18:35:51Z

@copilot expand unit tests

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

dmccoystephenson · 2026-02-08T19:05:28Z

@copilot review documentation for accuracy and include the core game loop

Copilot

Pull request overview

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

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

Copilot · 2026-02-08T19:06:14Z

+    // Internal method for direct access to armies list for modifications
+    public List<Army> getArmiesInternal() {
+        return armies;
+    }


getArmiesInternal() is a public JavaBean-style getter, so Spring/Jackson will serialize it as an armiesInternal field in API responses (and it also exposes the mutable internal list). If this is intended only for in-service mutations, mark it @JsonIgnore (or rename away from get* / make it non-serializable) and avoid exposing the mutable list on the public API surface.

Added @JsonIgnore annotation to getArmiesInternal() to prevent it from being serialized in API responses and exposing the mutable internal list. Commit: 753c34a

Copilot · 2026-02-08T19:06:14Z

+    public synchronized GameState getState() {
+        return gameState;
+    }


getState() returns the live, mutable gameState instance. Even with synchronized methods, Spring serializes the returned object to JSON after the controller method exits (outside the lock), so another request can mutate the state during serialization, leading to inconsistent responses or ConcurrentModificationException. Prefer returning a snapshot/DTO created under the service lock (deep-copy grid + armies) and have controllers return that snapshot instead of the shared instance.

Modified getState() to return a deep-copy snapshot of the game state created under the synchronized lock. Added Army copy constructor to preserve IDs during copying. This prevents ConcurrentModificationException during Spring's JSON serialization and ensures thread-safe state access. Added 3 new tests to verify snapshot behavior. Commit: 753c34a

…hitecture Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot · 2026-02-08T19:08:28Z

@copilot review documentation for accuracy and include the core game loop

Reviewed and enhanced documentation with comprehensive "Core Game Loop" section including:

New Sections:

Detailed tick-based game loop with 4 phases: Tick Increment, Soldier Generation, Combat Resolution, Cleanup
Step-by-step pseudocode for each phase
Example turn sequence demonstrating full gameplay cycle
API request/response structure examples (JSON)
Expanded Architecture section with technical details
Technical Constraints section clarifying prototype limitations

Accuracy Updates:

Clarified single-player nature with AI-controlled enemies (Player 2)
Updated player descriptions (Player 1 = human/blue, Player 2 = AI/red)
Added CI/CD documentation (41 tests, GitHub Actions)
Documented thread safety, CORS restrictions, and connection management
Verified all technical details match actual implementation

All builds verified. Commit: 0c3698b

dmccoystephenson · 2026-02-08T19:09:01Z

@copilot address comments

…ate snapshots Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

dmccoystephenson · 2026-02-08T20:15:13Z

@copilot Include mvnw so that the developer does not need to have mvn installed. Also include a start-frontend.bat script, since WSL doesn't have a display

…pment Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot · 2026-02-08T20:18:21Z

@copilot Include mvnw so that the developer does not need to have mvn installed. Also include a start-frontend.bat script, since WSL doesn't have a display

Added Maven Wrapper (mvnw) to both backend and frontend projects - Maven installation is now optional. Created Windows batch scripts:

start-backend.bat - starts backend on Windows
start-frontend.bat - starts frontend on Windows (native Windows, not WSL)

Updated all shell scripts to use ./mvnw by default. Added README documentation covering:

Maven Wrapper usage for both options (mvnw vs mvn)
Separate sections for Unix/Linux/macOS and Windows quick start scripts
Note about WSL display limitations and X server requirement for WSL users

Commit: 0cbc0fc

dmccoystephenson · 2026-02-08T20:27:50Z

@copilot This prototype isn’t very engaging yet. From a player’s perspective, I should be able to:

Select a destination for an army and watch it move (e.g. 1 tile per tick)
Station armies in villages and build them up over time
See the size/composition of each army
Split an army into multiple armies
Capture rival castles or engage enemy armies in battle

There should also be clear win/lose conditions:

Win by capturing all castles
Lose by losing all owned land

All of the above is out of scope for this PR. Please draft an MVP.md document that clearly outlines the features, mechanics, and tasks required to reach this minimum viable version of the game.

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot · 2026-02-08T20:30:14Z

@copilot This prototype isn’t very engaging yet. From a player’s perspective, I should be able to:

Select a destination for an army and watch it move (e.g. 1 tile per tick)
...

Created comprehensive MVP.md document outlining the path from current prototype to engaging gameplay. The document includes:

6 Core Features:

Army Movement & Pathfinding - 1 tile/tick with A* pathfinding
Army Management - Split/merge armies, display soldier counts
Territory Control - Village ownership and capture mechanics
Castle Capture & Win Conditions - Win by capturing all castles
Basic AI Opponent - Rule-based AI for Player 2
Enhanced UI/UX - Mouse controls, tooltips, HUD, game log

3-Phase Roadmap:

Phase 1: Foundation (movement, ownership, visualization)
Phase 2: Strategy (army management, victory conditions)
Phase 3: Engagement (AI, polish, mouse controls)

Each feature includes detailed task breakdowns, backend/frontend changes needed, and test requirements. Estimated 130-185 hours total (4-6 weeks solo).

Commit: 6d3d60a

dmccoystephenson · 2026-02-08T20:40:03Z

@copilot Excellent, now provide corresponding TICKETS.md document oriented towards Copilot Coding Agent that contains titles & descriptions that we can create GitHub issues from. No need to be super granular, it should not take 50 agent sessions to complete this.

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot · 2026-02-08T20:42:34Z

@copilot Excellent, now provide corresponding TICKETS.md document oriented towards Copilot Coding Agent that contains titles & descriptions that we can create GitHub issues from. No need to be super...

Created TICKETS.md with 7 substantial GitHub issue templates optimized for Copilot Coding Agent:

Ticket Structure:

Army Movement System (2-3 sessions) - Pathfinding, tile-by-tile movement
Territory Control (2 sessions) - Village ownership, capture mechanics
Army Management (2 sessions) - Split/merge, soldier count display
Castle Capture & Win Conditions (2 sessions) - Victory/defeat, 3-tick capture timer
Rule-Based AI Opponent (3 sessions) - Decision logic, target evaluation
Enhanced UI & Mouse Controls (3 sessions) - Click-to-move, HUD, tooltips
Polish & Integration Testing (2 sessions) - Balance, performance, documentation

Total: 16-20 agent sessions (vs 50+ with granular tickets)

Each ticket includes:

Concrete acceptance criteria (backend/frontend/docs)
Technical implementation notes
Specific file paths to modify
Clear dependencies and sequencing
Test requirements (80% coverage target)

Ready to copy directly into GitHub issues with labels (enhancement, mvp, backend, frontend).

Commit: 43aba10

Initial plan

cb7650b

Copilot AI assigned Copilot and dmccoystephenson Feb 8, 2026

Copilot started work on behalf of dmccoystephenson February 8, 2026 16:59 View session

Copilot AI and others added 3 commits February 8, 2026 17:03

Create backend and frontend projects with basic functionality

fc6d108

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Add startup scripts, demo, and complete documentation

54a550c

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Fix resource leaks and concurrent modification issues

d5a6cec

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Create minimal client/server prototype using Java Spring Boot and LWJGL~~ Implement minimal client/server game prototype with Spring Boot backend and LWJGL frontend Feb 8, 2026

Copilot AI requested a review from dmccoystephenson February 8, 2026 17:11

Copilot finished work on behalf of dmccoystephenson February 8, 2026 17:11

dmccoystephenson requested a review from Copilot February 8, 2026 17:47

Copilot started reviewing on behalf of dmccoystephenson February 8, 2026 17:47 View session

Copilot AI reviewed Feb 8, 2026

View reviewed changes

Copilot started work on behalf of dmccoystephenson February 8, 2026 18:04 View session

Copilot AI and others added 2 commits February 8, 2026 18:11

Address code review feedback: add timeouts, UTF-8, cross-platform sup…

66c55d0

…port, thread safety, stable army IDs, and CORS restrictions Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Fix thread-safe Army ID counter, rename armyIndex to armyId, remove R…

18100a8

…EADME duplicates Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot finished work on behalf of dmccoystephenson February 8, 2026 18:16

Copilot started work on behalf of dmccoystephenson February 8, 2026 18:18 View session

Add CI workflow and unit tests for frontend and backend

5de53c7

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot finished work on behalf of dmccoystephenson February 8, 2026 18:22

Copilot started work on behalf of dmccoystephenson February 8, 2026 18:29 View session

Copilot finished work on behalf of dmccoystephenson February 8, 2026 18:30

Copilot started work on behalf of dmccoystephenson February 8, 2026 18:36 View session

Expand unit tests for backend and frontend models and services

05ad8c9

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot started reviewing on behalf of dmccoystephenson February 8, 2026 19:01 View session

Copilot started work on behalf of dmccoystephenson February 8, 2026 19:05 View session

Copilot AI reviewed Feb 8, 2026

View reviewed changes

Review and enhance documentation with detailed core game loop and arc…

0c3698b

…hitecture Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot finished work on behalf of dmccoystephenson February 8, 2026 19:09

Copilot started work on behalf of dmccoystephenson February 8, 2026 19:09 View session

Fix thread safety: add @JsonIgnore to getArmiesInternal and return st…

753c34a

…ate snapshots Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot finished work on behalf of dmccoystephenson February 8, 2026 19:13

Copilot started work on behalf of dmccoystephenson February 8, 2026 20:15 View session

Add Maven Wrapper and Windows batch scripts for cross-platform develo…

0cbc0fc

…pment Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot finished work on behalf of dmccoystephenson February 8, 2026 20:19

Copilot started work on behalf of dmccoystephenson February 8, 2026 20:28 View session

Add MVP.md document outlining features and tasks for engaging gameplay

6d3d60a

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

Copilot finished work on behalf of dmccoystephenson February 8, 2026 20:30

Copilot started work on behalf of dmccoystephenson February 8, 2026 20:40 View session

Add TICKETS.md with GitHub issue templates for MVP implementation

43aba10

Co-authored-by: dmccoystephenson <21204351+dmccoystephenson@users.noreply.github.com>

dmccoystephenson marked this pull request as ready for review February 8, 2026 20:43

Copilot finished work on behalf of dmccoystephenson February 8, 2026 20:43

dmccoystephenson merged commit bcf5e4d into main Feb 8, 2026
2 checks passed

dmccoystephenson deleted the copilot/create-basic-client-server-prototype branch February 11, 2026 05:26

Copilot AI mentioned this pull request Feb 15, 2026

Add Spring Boot web client with Docker Compose orchestration and CI integration #30

Merged

14 tasks

	@CrossOrigin(origins = "*")
	@CrossOrigin(origins = {"http://localhost:3000", "http://127.0.0.1:3000"})

Conversation

Copilot AI commented Feb 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

dmccoystephenson commented Feb 8, 2026

Uh oh!

dmccoystephenson commented Feb 8, 2026

Uh oh!

Copilot AI commented Feb 8, 2026

Uh oh!

dmccoystephenson commented Feb 8, 2026

Uh oh!

Copilot AI commented Feb 8, 2026

Uh oh!

dmccoystephenson commented Feb 8, 2026

Uh oh!

dmccoystephenson commented Feb 8, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 8, 2026

Choose a reason for hiding this comment

Copilot AI commented Feb 8, 2026 •

edited

Loading