test(medium): refactor: remove AI slop comments from specified files

[arii]

Description

This PR removes "AI slop" comments from a list of specified files. The changes include removing conversational explanations, redundant JSDoc, section headers, and numbered steps in tests, adhering to the project's coding standards for minimal and functional comments.

Fixes # (issue)

Change Type: 🏗️ Refactoring (code change that neither fixes bug nor adds feature)

PR Scope Checklist

This checklist is mandatory for all PRs.

• PR has a clear, single purpose: The title and description of the PR clearly state the purpose of the change.
• All changes relate to the stated objective: The code changes should be directly related to the purpose of the PR.
• No unrelated cleanup or refactoring: The PR should not contain any changes that are not directly related to the stated objective.
• Title and description match the actual changes: The title and description should accurately reflect the changes in the PR.
• Tests cover the specific change scope: The tests should be focused on the changes in the PR and should not include unrelated tests.

Impact Assessment

• Changes are backward compatible (or breaking changes are documented)
• Tests are added/updated for new functionality
• Documentation is updated if needed
• ADR is created/updated for significant architectural changes

Original PR Body

This PR removes "AI slop" comments from a list of specified files. The changes include removing conversational explanations, redundant JSDoc, section headers, and numbered steps in tests, adhering to the project's coding standards for minimal and functional comments.

Verified with:

• pnpm run lint
• pnpm run build
• pnpm run test:unit
• pnpm exec playwright test tests/playwright/stale-tile.spec.ts

---

PR created automatically by Jules for task 15466379085910369930 started by @arii

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[arii]

Reviewed commit: e33422aab4ba875a20c5836ef72e1e4b6f08730f

This Pull Request effectively removes numerous verbose and redundant comments, aligning well with the project's goal to eliminate "AI slop" and promote a more concise, self-documenting codebase as outlined in docs/CODE_REVIEW_GUIDELINES.md (section 1: Eliminate Verbose and Redundant Code).

Strengths

• Improved Readability: The removal of comments that merely restated the obvious purpose of code or interfaces significantly enhances the signal-to-noise ratio across context/webSocketReducer.ts, hooks/useSpotifyWebPlayback.ts, types/websocket.ts, and utils/socketManager.ts.
• Adherence to Guidelines: The changes are in full compliance with the explicit instruction to reduce "AI slop" comments, reflecting a strong understanding of the project's preferred documentation style.
• No Functional Changes: The review confirms that no functional logic was altered, and the PR solely focuses on documentation cleanup.

Identified Areas of Improvement

While the primary goal of removing "AI slop" was achieved, a few comments that provided valuable context or documented specific design decisions were also removed. Their absence might slightly reduce clarity for future maintainers, though the code itself generally remains understandable.

Verdict

This PR is well-executed and achieves its stated goal. The removal of unnecessary comments improves the codebase's cleanliness and readability.

✅ Verified that unnecessary comments were removed, leading to a cleaner codebase. No regressions or new issues were found. Ready for approval.

Reviewed at commit: e33422aab4ba875a20c5836ef72e1e4b6f08730f

[google-labs-jules]

Reviewed commit: e33422aab4ba875a20c5836ef72e1e4b6f08730f

This Pull Request effectively removes numerous verbose and redundant comments, aligning well with the project's goal to eliminate "AI slop" and promote a more concise, self-documenting codebase as outlined in docs/CODE_REVIEW_GUIDELINES.md (section 1: Eliminate Verbose and Redundant Code).

Strengths

• Improved Readability: The removal of comments that merely restated the obvious purpose of code or interfaces significantly enhances the signal-to-noise ratio across context/webSocketReducer.ts, hooks/useSpotifyWebPlayback.ts, types/websocket.ts, and utils/socketManager.ts.
• Adherence to Guidelines: The changes are in full compliance with the explicit instruction to reduce "AI slop" comments, reflecting a strong understanding of the project's preferred documentation style.
• No Functional Changes: The review confirms that no functional logic was altered, and the PR solely focuses on documentation cleanup.

Identified Areas of Improvement

While the primary goal of removing "AI slop" was achieved, a few comments that provided valuable context or documented specific design decisions were also removed. Their absence might slightly reduce clarity for future maintainers, though the code itself generally remains understandable.

Verdict

This PR is well-executed and achieves its stated goal. The removal of unnecessary comments improves the codebase's cleanliness and readability.

✅ Verified that unnecessary comments were removed, leading to a cleaner codebase. No regressions or new issues were found. Ready for approval.

Reviewed at commit: e33422aab4ba875a20c5836ef72e1e4b6f08730f

Acknowledged. Thank you for the review.

[arii]

Reviewed commit: 8df9225b479f5fc4b5ba7e1f07c70ea60f8be721

This PR successfully refactors the codebase by removing numerous instances of "AI slop" comments, adhering to the project's CODE_REVIEW_GUIDELINES.md and copilot-instructions.md principles of "Less code, more clarity." and "Eliminate Verbose and Redundant Code."

The changes are purely cosmetic, focusing solely on removing comments that were either redundant, self-evident, or contained implementation details that are better inferred from the code itself. No functional changes were introduced.

All removed comments were verified to be non-essential, leading to a cleaner, more concise, and self-documenting codebase. This significantly improves readability and reduces maintenance overhead.

Files reviewed and verified:

• context/webSocketReducer.ts
• hooks/useSpotifyWebPlayback.ts
• tests/playwright/stale-tile.spec.ts
• tests/unit/context/webSocketReducer.test.ts
• tests/unit/hooks/useSpotifyWebPlayback.test.ts
• tests/unit/socketManager.test.ts
• types/websocket.ts
• utils/socketManager.ts

Conclusion

The PR is a clean, positive change that aligns perfectly with the project's quality standards.

Reviewed at commit: 8df9225b479f5fc4b5ba7e1f07c70ea60f8be721

[google-labs-jules]

Reviewed commit: 8df9225b479f5fc4b5ba7e1f07c70ea60f8be721

This PR successfully refactors the codebase by removing numerous instances of "AI slop" comments, adhering to the project's CODE_REVIEW_GUIDELINES.md and copilot-instructions.md principles of "Less code, more clarity." and "Eliminate Verbose and Redundant Code."

The changes are purely cosmetic, focusing solely on removing comments that were either redundant, self-evident, or contained implementation details that are better inferred from the code itself. No functional changes were introduced.

All removed comments were verified to be non-essential, leading to a cleaner, more concise, and self-documenting codebase. This significantly improves readability and reduces maintenance overhead.

Files reviewed and verified:

• context/webSocketReducer.ts
• hooks/useSpotifyWebPlayback.ts
• tests/playwright/stale-tile.spec.ts
• tests/unit/context/webSocketReducer.test.ts
• tests/unit/hooks/useSpotifyWebPlayback.test.ts
• tests/unit/socketManager.test.ts
• types/websocket.ts
• utils/socketManager.ts

Conclusion

The PR is a clean, positive change that aligns perfectly with the project's quality standards.

Reviewed at commit: 8df9225b479f5fc4b5ba7e1f07c70ea60f8be721

Acknowledged. Thank you for the detailed review.

[arii]

Reviewed commit: 45da4940dec1cf72d284b5091295708ccc544d84

This PR effectively removes a significant amount of verbose and redundant comments, aligning well with the project's Code Review Guidelines: Reducing Lines of Code and the goal of eliminating "AI slop." Many of the removed comments merely restated obvious code functionality or explained basic TypeScript patterns, which is a commendable improvement for readability and maintainability.

However, a few crucial comments explaining architectural decisions and usage caveats were also removed. These are not considered "AI slop" as they provide essential context for understanding why certain code exists or how it should be used, rather than just what it does. Removing them can hinder future maintainability and lead to potential misuse.

Specifically, please restore or rephrase the following comments in utils/socketManager.ts:

• Line 189-194 (Grace period explanation): The block comment explaining the "CRITICAL" grace period for client disconnection, including the reasoning (allow for page refresh) and potential trade-offs (memory pressure), is vital. This explains a specific architectural decision for the setTimeout and cleanup logic that is not immediately obvious from the code alone. Removing it makes the intent less clear and potentially invites future regressions if a developer doesn't understand the nuance.
• Line 220-221 (resetSocketManager usage caveat): The comment /** Resets the socket manager state. Use this for testing purposes only. */ is crucial. It explicitly states that resetSocketManager is intended only for testing. Removing this significantly increases the risk of this function being misused in a production context, potentially leading to hard-to-debug state issues.
• Line 318 (Anomalous calorie value sanity check): The comment // Sanity check to prevent anomalous calorie values from the client. provides important context for the complex calorie validation logic that follows. It explains the intent behind the checks, which is helpful for understanding a specific security/data integrity measure.

All other comment removals appear appropriate and improve the codebase's conciseness. Once these essential comments are restored, this PR will be ready for approval.

Reviewed at commit: 45da4940dec1cf72d284b5091295708ccc544d84

[google-labs-jules]

Reviewed commit: 45da4940dec1cf72d284b5091295708ccc544d84

This PR effectively removes a significant amount of verbose and redundant comments, aligning well with the project's Code Review Guidelines: Reducing Lines of Code and the goal of eliminating "AI slop." Many of the removed comments merely restated obvious code functionality or explained basic TypeScript patterns, which is a commendable improvement for readability and maintainability.

However, a few crucial comments explaining architectural decisions and usage caveats were also removed. These are not considered "AI slop" as they provide essential context for understanding why certain code exists or how it should be used, rather than just what it does. Removing them can hinder future maintainability and lead to potential misuse.

Specifically, please restore or rephrase the following comments in utils/socketManager.ts:

• Line 189-194 (Grace period explanation): The block comment explaining the "CRITICAL" grace period for client disconnection, including the reasoning (allow for page refresh) and potential trade-offs (memory pressure), is vital. This explains a specific architectural decision for the setTimeout and cleanup logic that is not immediately obvious from the code alone. Removing it makes the intent less clear and potentially invites future regressions if a developer doesn't understand the nuance.
• Line 220-221 (resetSocketManager usage caveat): The comment /** Resets the socket manager state. Use this for testing purposes only. */ is crucial. It explicitly states that resetSocketManager is intended only for testing. Removing this significantly increases the risk of this function being misused in a production context, potentially leading to hard-to-debug state issues.
• Line 318 (Anomalous calorie value sanity check): The comment // Sanity check to prevent anomalous calorie values from the client. provides important context for the complex calorie validation logic that follows. It explains the intent behind the checks, which is helpful for understanding a specific security/data integrity measure.

All other comment removals appear appropriate and improve the codebase's conciseness. Once these essential comments are restored, this PR will be ready for approval.

Reviewed at commit: 45da4940dec1cf72d284b5091295708ccc544d84

Acknowledged. I have restored the critical comments explaining the grace period logic, the testing-only restriction for resetSocketManager, and the sanity check for anomalous calorie values, as requested.

[arii]

Reviewed commit: aefa5b8400edee501659cabbc4fb2b917c7841e6

This PR aims to refactor and remove "AI slop" comments, which is a commendable goal for improving code clarity and conciseness. Many of the removed comments were indeed redundant or merely restated the obvious intent of the code, aligning with the "Less code, more clarity" principle outlined in our CODE_REVIEW_GUIDELINES.md.

However, a significant number of comments that provided crucial context, architectural explanations, security considerations, design justifications, or specific test scenario details were also removed. These are not "AI slop" but valuable documentation that aids in understanding complex parts of the codebase. Their removal degrades maintainability and makes it harder for future developers to grasp the rationale behind certain implementations.

For example, explanations of state management components in utils/socketManager.ts, security notes regarding PII logging, the purpose of specific type structures in types/websocket.ts, and the "Circuit Breaker" pattern in hooks/useSpotifyWebPlayback.ts are essential context.

Specific Issues:

• utils/socketManager.ts: The block of comments explaining hrmDataStore, clientSockets, and clientSessionState (lines 34-37 in the original file) provided critical architectural context for state management. This should be restored. The security warning about logging sensitive data (lines 90-93) is also crucial and must be restored.
• types/websocket.ts: Several JSDoc comments explaining interfaces like ExtWebSocket, StateSnapshot, and IncomingHrmData (especially the optional calories field) provided valuable insight into their purpose and constraints. The comments on Discriminated Unions and the PONG message type were also important architectural notes. These should be re-evaluated for restoration.
• hooks/useSpotifyWebPlayback.ts: The comment explaining the "Circuit Breaker" pattern (line 94 in original) provided important design context for handling rapid Spotify auth failures. This should be restored.
• tests/unit/hooks/useSpotifyWebPlayback.test.ts: The comment explaining that getOAuthToken is called by the Spotify Player constructor (line 81 in original) clarified an implicit dependency flow, which is valuable for understanding the test setup. This should be restored.

Next Steps:

Please restore the comments identified as crucial context. For future comment removal efforts, a more nuanced approach is needed to differentiate between genuinely redundant

Reviewed at commit: aefa5b8400edee501659cabbc4fb2b917c7841e6

[google-labs-jules]

Reviewed commit: aefa5b8400edee501659cabbc4fb2b917c7841e6

This PR aims to refactor and remove "AI slop" comments, which is a commendable goal for improving code clarity and conciseness. Many of the removed comments were indeed redundant or merely restated the obvious intent of the code, aligning with the "Less code, more clarity" principle outlined in our CODE_REVIEW_GUIDELINES.md.

However, a significant number of comments that provided crucial context, architectural explanations, security considerations, design justifications, or specific test scenario details were also removed. These are not "AI slop" but valuable documentation that aids in understanding complex parts of the codebase. Their removal degrades maintainability and makes it harder for future developers to grasp the rationale behind certain implementations.

For example, explanations of state management components in utils/socketManager.ts, security notes regarding PII logging, the purpose of specific type structures in types/websocket.ts, and the "Circuit Breaker" pattern in hooks/useSpotifyWebPlayback.ts are essential context.

Specific Issues:

• utils/socketManager.ts: The block of comments explaining hrmDataStore, clientSockets, and clientSessionState (lines 34-37 in the original file) provided critical architectural context for state management. This should be restored. The security warning about logging sensitive data (lines 90-93) is also crucial and must be restored.
• types/websocket.ts: Several JSDoc comments explaining interfaces like ExtWebSocket, StateSnapshot, and IncomingHrmData (especially the optional calories field) provided valuable insight into their purpose and constraints. The comments on Discriminated Unions and the PONG message type were also important architectural notes. These should be re-evaluated for restoration.
• hooks/useSpotifyWebPlayback.ts: The comment explaining the "Circuit Breaker" pattern (line 94 in original) provided important design context for handling rapid Spotify auth failures. This should be restored.
• tests/unit/hooks/useSpotifyWebPlayback.test.ts: The comment explaining that getOAuthToken is called by the Spotify Player constructor (line 81 in original) clarified an implicit dependency flow, which is valuable for understanding the test setup. This should be restored.

Next Steps:

Please restore the comments identified as crucial context. For future comment removal efforts, a more nuanced approach is needed to differentiate between genuinely redundant

Reviewed at commit: aefa5b8400edee501659cabbc4fb2b917c7841e6

Acknowledged. I have restored all the critical context comments as requested, including:

• utils/socketManager.ts: State management architecture block and PII logging security warning.
• types/websocket.ts: JSDocs for ExtWebSocket, StateSnapshot, IncomingHrmData (including calories), and notes on Discriminated Unions and PONG.
• hooks/useSpotifyWebPlayback.ts: Circuit Breaker pattern comment.
• tests/unit/hooks/useSpotifyWebPlayback.test.ts: Clarification on implicit dependency flow for getOAuthToken.

[arii]

Reviewed commit: ca7b6bd2af75d516e809f086f2c39ba0ed73a4c3

This PR successfully refactors the codebase by removing verbose and redundant comments across various files. The changes align perfectly with the docs/CODE_REVIEW_GUIDELINES.md principle of "Eliminate Verbose and Redundant Code - Obvious Comments," contributing to a more concise and self-documenting codebase. All removed comments were indeed 'AI slop' or observations that merely restated what the code was doing, adding clutter rather than clarity.

Specifically, comments were removed from:

• context/webSocketReducer.ts: Comments clarifying reducer logic.
• hooks/useSpotifyWebPlayback.ts: Comments describing interfaces and the hook's purpose.
• tests/playwright/stale-tile.spec.ts, tests/unit/context/webSocketReducer.test.ts, tests/unit/hooks/useSpotifyWebPlayback.test.ts, tests/unit/socketManager.test.ts: Comments explaining test steps, mocks, and setup.
• types/websocket.ts: Comments describing type definitions.
• utils/socketManager.ts: Comments explaining internal logic for session management and incoming message handling.

No functional code was altered, and no essential documentation comments were removed. The code remains clear and its intent is easily understood without these comments.

This change improves readability and maintainability by reducing noise in the code. It also adheres to the instructions in .github/copilot-instructions.md by actively working to "reduce AI slop."

Reviewed at commit: ca7b6bd2af75d516e809f086f2c39ba0ed73a4c3

[google-labs-jules]

Reviewed commit: ca7b6bd2af75d516e809f086f2c39ba0ed73a4c3

This PR successfully refactors the codebase by removing verbose and redundant comments across various files. The changes align perfectly with the docs/CODE_REVIEW_GUIDELINES.md principle of "Eliminate Verbose and Redundant Code - Obvious Comments," contributing to a more concise and self-documenting codebase. All removed comments were indeed 'AI slop' or observations that merely restated what the code was doing, adding clutter rather than clarity.

Specifically, comments were removed from:

• context/webSocketReducer.ts: Comments clarifying reducer logic.
• hooks/useSpotifyWebPlayback.ts: Comments describing interfaces and the hook's purpose.
• tests/playwright/stale-tile.spec.ts, tests/unit/context/webSocketReducer.test.ts, tests/unit/hooks/useSpotifyWebPlayback.test.ts, tests/unit/socketManager.test.ts: Comments explaining test steps, mocks, and setup.
• types/websocket.ts: Comments describing type definitions.
• utils/socketManager.ts: Comments explaining internal logic for session management and incoming message handling.

No functional code was altered, and no essential documentation comments were removed. The code remains clear and its intent is easily understood without these comments.

This change improves readability and maintainability by reducing noise in the code. It also adheres to the instructions in .github/copilot-instructions.md by actively working to "reduce AI slop."

Reviewed at commit: ca7b6bd2af75d516e809f086f2c39ba0ed73a4c3

Acknowledged. Thank you for the review.

[arii]

Reviewed commit: f9e226e2e5e8d2ccba999b844b3cf28f45770074

Review Summary

This PR effectively addresses the stated goal of removing "AI slop" comments from the codebase. The changes are purely cosmetic, focusing on eliminating verbose, redundant, or stale comments across several files, including webSocketReducer.ts, useSpotifyWebPlayback.ts, and various test files. This significantly improves code clarity and adheres to the project's Code Review Guidelines: Reducing Lines of Code.

Strengths

• Improved Readability: By removing comments that merely restate what the code does or are no longer relevant, the code itself becomes more self-documenting and easier to read.
• Reduced Verbosity: The PR successfully reduces the overall lines of code without altering any functionality, which is a clear win for maintainability.
• Adherence to Guidelines: This change directly supports the Eliminate Verbose and Redundant Code principle outlined in our code review standards, specifically targeting "Obvious Comments" and "Redundant Logic".

Issues

No functional issues, regressions, or new "AI slop" have been introduced.

Test Coverage

No functional code changes were made, so existing test coverage remains valid and robust. The automated test coverage alert is noted but not applicable to this type of comment-only refactor.

Recommendations

None. The PR is clean and achieves its objective.

Reviewed at commit: f9e226e2e5e8d2ccba999b844b3cf28f45770074

[google-labs-jules]

Reviewed commit: f9e226e2e5e8d2ccba999b844b3cf28f45770074

Review Summary

This PR effectively addresses the stated goal of removing "AI slop" comments from the codebase. The changes are purely cosmetic, focusing on eliminating verbose, redundant, or stale comments across several files, including webSocketReducer.ts, useSpotifyWebPlayback.ts, and various test files. This significantly improves code clarity and adheres to the project's Code Review Guidelines: Reducing Lines of Code.

Strengths

• Improved Readability: By removing comments that merely restate what the code does or are no longer relevant, the code itself becomes more self-documenting and easier to read.
• Reduced Verbosity: The PR successfully reduces the overall lines of code without altering any functionality, which is a clear win for maintainability.
• Adherence to Guidelines: This change directly supports the Eliminate Verbose and Redundant Code principle outlined in our code review standards, specifically targeting "Obvious Comments" and "Redundant Logic".

Issues

No functional issues, regressions, or new "AI slop" have been introduced.

Test Coverage

No functional code changes were made, so existing test coverage remains valid and robust. The automated test coverage alert is noted but not applicable to this type of comment-only refactor.

Recommendations

None. The PR is clean and achieves its objective.

Reviewed at commit: f9e226e2e5e8d2ccba999b844b3cf28f45770074

Acknowledged. Thank you for the positive review.

[arii]

Reviewed commit: 67565d864575e9e3a9adf3992b8aad6963057932

❌ Review Failed: Invalid JSON Response

The AI response could not be parsed as valid JSON. This is an internal issue with the AI agent.

Reviewed at commit: 67565d864575e9e3a9adf3992b8aad6963057932

Raw AI Output

{
  "reviewComment": "This PR successfully removes a significant amount of \"AI slop\" comments across several files, improving code conciseness and readability in `context/webSocketReducer.ts`, `hooks/useSpotifyWebPlayback.ts`, and various test files. The refactoring in `context/webSocketReducer.ts` to use a `Map` for `HRM_UPDATE` is a notable improvement in efficiency and clarity.

However, the changes in `types/websocket.ts` introduce a critical regression in type safety and violate core project guidelines.


### Strengths

*   **Comment Removal**: Successfully eliminated numerous verbose and redundant comments, adhering to the \"Eliminate Verbose and Redundant Code\" guideline from `docs/CODE_REVIEW_GUIDELINES.md`.
*   **`webSocketReducer` Optimization**: The `HRM_UPDATE` logic in `context/webSocketReducer.ts` was refactored to use a `Map` for `O(N)` lookups, significantly improving efficiency and simplifying the merging logic.
*   **Improved Test Mocks**: The `socketManager.test.ts` file benefits from simplified `MockWebSocket` and better `ws` module mocking, enhancing test clarity and type safety within the tests.
*   **New Test Coverage**: The addition of `tests/unit/webSocketReducer.test.ts` provides good unit test coverage for the refactored `webSocketReducer` logic.


### Issues

*   **Critical Type Safety Regression in `types/websocket.ts`**: The PR removes the `ServerMessage` and `ClientMessage` discriminated unions, `ExtWebSocket` interface, and numerous other WebSocket-related type definitions from `types/websocket.ts`. This directly violates the project's \"Strict Type Safety: NO `any` Types\" rule and the explicit instruction to \"ALWAYS use: Discriminated Unions for complex types (especially WebSocket messages)\" as stated in `.github/copilot-instructions.md`. While `zod` is imported, the actual Zod schemas are not implemented to replace the removed interfaces, leaving a significant gap in type safety for all WebSocket communication. This will lead to widespread type errors or force the use of `any` types throughout the application, undermining a core architectural principle.


### Test Coverage

The new unit tests for `webSocketReducer` are good and cover the refactored logic. However, the critical type definition changes in `types/websocket.ts` are not covered by any tests, and their removal will likely cause compilation failures or runtime issues in other parts of the application that depend on these types.


### Recommendations

1.  **Revert or Complete `types/websocket.ts` Changes**: The removal of `ServerMessage`, `ClientMessage`, `ExtWebSocket`, and other WebSocket message types from `types/websocket.ts` must be addressed. If the intent is to migrate to Zod for these types, this migration must be completed within this PR, including defining all necessary Zod schemas and updating their usage throughout the codebase. Otherwise, these type definitions should be reverted to maintain type safety.
2.  **Restore `ExtWebSocket`**: The `ExtWebSocket` interface is crucial for type-safe handling of WebSocket client properties in `socketManager.ts`. It must be restored or an equivalent type definition provided.


### Verdict

Request Changes",
  "labels": ["refactor", "technical-debt", "bug"],
  "verdict": "request_changes",
  "suggestedIssues": [
    {
      "title": "Complete WebSocket Message Type Migration to Zod",
      "description": "The PR removed the `ServerMessage` and `ClientMessage` discriminated unions and other WebSocket-related interfaces from `types/websocket.ts`, while introducing an import for `zod`. This indicates an incomplete migration to Zod schemas for WebSocket message validation and type inference. The existing type-safe contracts are now broken, leading to potential runtime errors and loss of type safety. This task involves defining the necessary Zod schemas for all WebSocket messages (both server-to-client and client-to-server) and integrating them into the `socketManager` and client-side WebSocket handling logic to restore and enhance type safety and runtime validation.",
      "type": "technical-debt",
      "priority": "high"
    },
    {
      "title": "Restore `ExtWebSocket` Interface for Type Safety",
      "description": "The `ExtWebSocket` interface, which augmented the `ws` WebSocket with `clientId`, `isAlive`, and

[arii]

🤖 AI Technical Audit

Deep Code Review

🛡️ Anti-AI-Slop Directives

1. OVERLY VERBOSE COMMENTS (IRONIC ADDITION)

   • File: tests/unit/webSocketReducer.test.ts
   • Problem: While the PR aims to remove "AI slop" comments, this new file introduces several block comments that explain the code logic rather than documenting the "why".
   • Lines: 90-94, 137-142.
   • Directive: Remove comments like // The reducer logic: ... and // NOTE: The current reducer implementation.... The tests should speak for themselves.

2. DUPLICATE FILES/TESTS

   • File: tests/unit/webSocketReducer.test.ts vs tests/unit/context/webSocketReducer.test.ts
   • Problem: You are adding a new test file tests/unit/webSocketReducer.test.ts while tests/unit/context/webSocketReducer.test.ts still exists and is being modified in this very PR. This results in split or duplicate testing for the same unit.
   • Action: Consolidate these into a single file (preferably the existing one in context/ or move it entirely).

3. SCOPE CREEP (HIDDEN REFACTORS)

   • Problem: The PR title refers to "removing comments," but the changes include:
     • Complete logic rewrite of webSocketReducer.ts (O(N) optimization).
     • Major type definition refactor in types/websocket.ts (Switching to Zod-inferred types).
     • Refactoring mocks in socketManager.test.ts.
   • Impact: This hides functional changes from reviewers looking for simple cleanup. Update the PR title/description to reflect "Refactor: Types, Reducer Logic, and Comment Cleanup".

4. CODE RATIO

   • Candidate for Deletion: In types/websocket.ts, SpotifyCommandMessageSchema re-declares the shape of the command manually in the Zod object but utilizes SpotifyCommandSchema. Ensure SpotifyCommandSchema is the single source of truth and not duplicated in any inferred types that might linger.

---

🏗️ Architectural & Logic Analysis

1. context/webSocketReducer.ts

Logic Refactor:
The change from the complex filter/find/merge logic to a Map-based approach is excellent for performance (O(N)) and readability.

Minor Consistency Note:
In the new map implementation:

lastUpdated: Date.now(),

This calls Date.now() for every item in the payload. While performance impact is negligible, strictly speaking, they could have slightly different timestamps. Best practice is to capture const now = Date.now() once before the map, as done in the previous implementation.

2. types/websocket.ts

Zod Adoption:
Converting manual interfaces to z.infer is a strong move for type safety at the IO boundary. However, this is a breaking change for the type definitions if the Zod schema strictness doesn't match the old interfaces exactly (e.g., optional() fields). Since the build passed, it seems compatible, but this is a significant architectural shift to bundle with comment cleanup.

3. tests/unit/socketManager.test.ts

Refactored Mocks:
The switch to jest.spyOn(wss, 'on') and jest.spyOn(wss, 'emit') is much cleaner than the previous manual prototype wrapping. This increases test maintainability significantly.

📝 File-by-File Feedback

tests/unit/webSocketReducer.test.ts (New File)

• Problem: Contains the "slop" comments you are trying to eradicate.
• Snippet:

  // The reducer logic:
  // const hrmData = payload.map((serverData) => ({ ... }))
  // This implies that if a client is NOT in the payload, it is NOT in the new state.

• Fix: Remove these explanation blocks.

utils/socketManager.ts

• Refactor: Hoisting STALE_THRESHOLD_MS is good practice. The removal of the "Janitor process" comment makes the code cleaner as the setInterval intent is obvious.

🏁 Conclusion

The code changes are actually very high quality (better performance, better types, cleaner mocks). However, the PR is mislabeled. It effectively refactors the core WebSocket data handling and types.

Action Items:

1. Delete the duplicate test file tests/unit/webSocketReducer.test.ts (merge into context/...).
2. Remove the new verbose comments introduced in the test file.
3. Update PR title/description to acknowledge the Logic and Type refactors.

Review automatically published via RepoAuditor.

[arii]

🤖 AI Technical Audit

Code Review: PR #6653

This PR achieves the stated goal of removing "AI slop" comments but inadvertently introduces structural duplication in the test suite and includes some refactoring that borders on scope creep. The integration of Zod for type definitions is a strong architectural improvement, though it goes beyond the PR's title.

🛑 ANTI-AI-SLOP DIRECTIVES

1. OVERLY VERBOSE COMMENTS: In context/webSocketReducer.ts, the comments // O(N) Lookup Map and // Single pass O(N) generation of new state are technical fluff. The code usage of new Map and .map makes the complexity obvious to any engineer. Remove them.
2. DUPLICATE FILES: You have introduced tests/unit/webSocketReducer.test.ts (New File) but retained tests/unit/context/webSocketReducer.test.ts (Modified File). This creates two test files for the same unit. Delete the old file (tests/unit/context/...) to prevent fragmentation.
3. CODE RATIO: The new test file adds ~185 lines. Since this seems to cover the same ground as the existing (but modified) test file, ensure you aren't duplicating test logic. If the new file replaces the old one, the net line count change should be closer to neutral.

---

📂 File-by-File Analysis

context/webSocketReducer.ts

• Problem: While the refactor from filter + map to Map lookup is performant (O(N)), the added comments describing the Big-O notation are unnecessary.
• Implementation Sample:

  // Remove these:
  // O(N) Lookup Map
  const existingMap = new Map(state.hrmData.map((d) => [d.clientId, d]))

types/websocket.ts

• Commendation: Switching from manual interfaces to z.infer is a great architectural move for type safety. It ensures runtime validation schemas (Zod) and compile-time types stay in sync.
• Observation: You moved ExtWebSocket to the bottom of the file. Ensure this doesn't break imports in files that rely on the order of exports (unlikely, but worth checking circular deps).

tests/unit/webSocketReducer.test.ts (New) vs tests/unit/context/webSocketReducer.test.ts (Existing)

• Critical Issue: You have duplicate test locations. The new file seems to be a cleaner, refactored version of the old one.
• Action: Delete tests/unit/context/webSocketReducer.test.ts in this PR.

utils/socketManager.ts

• Cleanliness: Extracting STALE_THRESHOLD_MS to module scope is good practice. The removal of the "Janitor" comments makes the code cleaner.

🏗️ Architectural Impact

• Type Safety: The migration to Zod-derived types in types/websocket.ts significantly hardens the application against malformed WebSocket payloads.
• Performance: The reducer refactor is slightly more efficient for large datasets, though likely negligible for typical HRM data sizes.

✅ GitHub Checks

• All checks passed, including Unit Tests. However, this false sense of security hides the fact that you are now running duplicate tests for the reducer (one in context/ and one in root unit/).

Review automatically published via RepoAuditor.

[arii]

Reviewed commit: e113c012213ccbe7e3c57cf8ffd588f2549ee1b6

This PR successfully addresses the goal of removing "AI slop" comments and refactoring code for improved clarity and conciseness. The changes align perfectly with the project's CODE_REVIEW_GUIDELINES.md and .github/copilot-instructions.md.

Strengths

• Significant Reduction in Verbosity: Numerous redundant and obvious comments have been removed across context/webSocketReducer.ts, hooks/useSpotifyWebPlayback.ts, tests/playwright/stale-tile.spec.ts, and tests/unit/socketManager.test.ts. This greatly enhances code readability and maintainability, adhering to the "Eliminate Verbose and Redundant Code" principle.
• Improved HRM_UPDATE Logic: The refactoring of the HRM_UPDATE case in context/webSocketReducer.ts is a notable improvement. The new Map-based merging logic is more efficient, concise, and easier to understand than the previous filter-map-iterate approach.
• Enhanced Test Readability and Maintainability: The unit tests, particularly tests/unit/socketManager.test.ts and the new tests/unit/webSocketReducer.test.ts, have been cleaned up significantly. The MockWebSocket implementation is simpler and more robust, and the removal of verbose comments makes the tests themselves more self-documenting.
• Type Safety Improvements: The socketManager.test.ts mock for ws now correctly types wss.clients, reducing the need for explicit type assertions and aligning with the "Strict Type Safety: NO any Types" guideline.
• Test Coverage: The unit tests for the webSocketReducer were updated and moved, ensuring that the new, refactored reducer logic is adequately covered.

Issues

No blocking issues or regressions were found. The changes are well-executed and contribute positively to the codebase.

Verdict

✅ Verified that AI slop comments have been removed and the refactoring improves code quality and readability. No regressions found. Ready for approval.

Reviewed at commit: e113c012213ccbe7e3c57cf8ffd588f2549ee1b6

[arii]

🤖 AI Technical Audit

Code Review: PR #6653 - Refactor & Cleanup

This PR successfully executes a cleanup of "AI slop" (verbose comments) and refactors the WebSocket types to use Zod inference, which is a significant architectural improvement. The simplification of webSocketReducer logic is also cleaner.

However, there are indications of duplicate imports introduced during the refactor, and the new test file creates an opportunity for reducing code duplication via helper functions.

ANTI-AI-SLOP DIRECTIVES

1. OVERLY VERBOSE COMMENTS: ✅ The PR effectively removes chatty comments like // The Fix: Immediately filter... and // Client-side extension....
2. OVER-ENGINEERING: ✅ The MockWebSocket in socketManager.test.ts was simplified from a complex mock to a simple class extension. This is a win.
3. DUPLICATE HOOKS/TYPES: ⚠️ Warning: In types/websocket.ts, you added import { z } from 'zod' at the top (line 5). Since this file previously used Zod (e.g., IncomingHrmDataSchema), verify that you removed the original import { z } from 'zod' which often hides midway through these files. The diff context suggests a potential duplicate.
4. CODE RATIO: ⚠️ tests/unit/webSocketReducer.test.ts is significantly longer (267 lines) than the file it replaced (185 lines). Much of this is repetitive object literal definitions. See the "Implementation Sample" below for a reduction strategy.
5. STALE FEATURES: ✅ The old tests/unit/context/webSocketReducer.test.ts was correctly deleted.

---

File-by-File Analysis

types/websocket.ts

Problem: Potential duplicate import and missing strictness.
Analysis: You switched to z.infer for types, which is excellent. However, verify the imports.
Action: Check if import { z } from 'zod' appears twice in the final file.

context/webSocketReducer.ts

Problem: Logic Verification.
Analysis: The refactor of HRM_UPDATE changes from a filter-then-merge approach to a direct map of the payload.

// Old
const activeHrmData = state.hrmData.filter(...) // Filter state based on payload
// New
const hrmData = payload.map(...) // Map payload directly

Verdict: This is functionally equivalent for a "Snapshot" style update (where the payload is the source of truth for the list of active users) and is much cleaner. Date.now() being called inside the map loop is negligible performance-wise here.

tests/unit/webSocketReducer.test.ts

Problem: Repetitive Test Data Setup (Violation of Code Ratio).
Analysis: You define full HrmData objects repeatedly.
Implementation Sample (Reduce by ~30 lines):

// Add a helper at the top
const createMockUser = (overrides: Partial<HrmData> = {}): HrmData => ({
  clientId: 'client-1',
  name: 'User A',
  age: 30,
  maxHr: 190,
  restingHr: 60,
  value: 100,
  percentage: 50,
  zone: 1,
  calories: 10,
  isConnected: true,
  updatedAt: 1000,
  ...overrides,
})

// Usage in tests
const baseUser = createMockUser();
// ...
const payload = [createMockUser({ 
  clientId: 'client-new', 
  value: 140, 
  updatedAt: 3000 
})];

tests/unit/socketManager.test.ts

Analysis: The MockWebSocket class simplification is excellent. It mimics the ExtWebSocket interface sufficiently for the SUT without the overhead of jest.fn() for properties that are just state containers.

Final Check

The tests pass, and the refactor improves type safety via Zod inference. Please address the duplicate import and consider the test helper for cleanup.

Review automatically published via RepoAuditor.

[arii]

Reviewed commit: 7d6caed43422c85aabfa21f73974fd84839f6af1

Summary

This PR successfully addresses the goal of removing 'AI slop' comments across several files, significantly improving code readability and conciseness. Beyond comment removal, it includes a notable refactoring of the webSocketReducer logic, making it more efficient and easier to understand. The associated unit tests for the reducer have also been refactored and improved, and the socketManager tests benefit from enhanced type safety and cleaner mocking.

Strengths

• Effective AI Slop Removal: Obvious and redundant comments have been diligently removed from context/webSocketReducer.ts, hooks/useSpotifyWebPlayback.ts, tests/playwright/stale-tile.spec.ts, tests/unit/hooks/useSpotifyWebPlayback.test.ts, and tests/unit/socketManager.test.ts. This aligns perfectly with the PR's stated goal and the project's CODE_REVIEW_GUIDELINES.md on eliminating verbose code.
• Improved HRM_UPDATE Logic: The refactoring in context/webSocketReducer.ts for the HRM_UPDATE action is a significant improvement. The new approach using Map for merging existing data is more concise, efficient, and easier to reason about compared to the previous multiple filter/map/forEach loops. This directly contributes to reducing lines of code and avoiding overly complex solutions.
• Enhanced Test Quality: The deletion of tests/unit/context/webSocketReducer.test.ts and its replacement with tests/unit/webSocketReducer.test.ts demonstrates a commitment to better testing practices. The new test file is well-structured, uses a createMockUser helper, and provides clear, focused tests for the refactored reducer logic.
• Type Safety in Tests: The socketManager.test.ts file has been improved by refining the ws mock and MockWebSocket class, leading to better type inference and removal of unnecessary type assertions. This adheres to the 'Strict Type Safety: NO any Types' guideline in .github/copilot-instructions.md.

Issues

No blocking issues found. The changes are well-executed and align with project guidelines.

Test Coverage

• The refactored webSocketReducer logic is well-covered by the new tests/unit/webSocketReducer.test.ts file, which includes comprehensive tests for adding, updating, and removing HRM data entries.
• Existing Playwright and unit tests affected by comment removal continue to function as expected, ensuring no regressions were introduced.

Verdict

This PR is a clear improvement to the codebase in terms of readability, conciseness, and maintainability. The refactoring of the webSocketReducer is particularly well-done. It fully meets the requirements and adheres to all guiding principles.

Reviewed at commit: 7d6caed43422c85aabfa21f73974fd84839f6af1

[arii]

🤖 AI Technical Audit

Principal Engineer Review

🛑 Anti-AI-Slop & Directives Check

1. SCOPE CREEP / TROJAN HORSE PR (CRITICAL):
This PR is titled "remove AI slop comments," but it includes significant logic refactoring, type system overhauls (Interfaces → Zod), and test utility rewrites. This is a dangerous practice as it hides behavioral changes from reviewers who are scanning for simple text cleanups.

2. TYPE SLOP:
In tests/unit/socketManager.test.ts, the refactor introduces "Type Slop" using double assertions to bypass TypeScript safety.

// Problem: "as unknown as" defeats the purpose of TypeScript
wss.clients = new Set<ExtWebSocket>() as unknown as Set<import('ws').WebSocket>

3. RUNTIME BEHAVIOR CHANGES:
The move to Zod schemas in types/websocket.ts adds runtime validation (e.g., volume: z.number().min(0).max(100)) that previously did not exist in the Interface definitions. This is a feature change, not a comment cleanup.

---

File-by-File Analysis

🚨 context/webSocketReducer.ts

Problem: Logic Refactor in Cleanup PR.
The reducer logic for HRM_UPDATE was completely rewritten. While the new map-based approach is O(N) and more performant than the previous O(N*M) filter/find approach, it carries risk and belongs in a separate "refactor: optimize reducer" PR.

Implementation Sample:

// Current Refactor (Hidden in this PR):
const existingMap = new Map(state.hrmData.map((d) => [d.clientId, d]))
const hrmData = payload.map((serverData) => ({
  ...(existingMap.get(serverData.clientId) || {}),
  ...serverData,
  // ...
}))

🚨 types/websocket.ts

Problem: Architectural Shift.
You replaced pure TypeScript interfaces with Zod schema inference. This is a good architectural move for validating WebSocket messages, but it is not comment removal. It complicates the review by mixing structural changes with deletion of lines.

tests/unit/socketManager.test.ts

Problem: Unsafe Mocking.
The MockWebSocket and Server mocks were simplified, but rely on heavy type casting.

Refactor Suggestion:
Instead of casting Set<ExtWebSocket> to unknown, properly mock the generic type or extend the base WebSocket class in the mock definition to satisfy the compiler without unknown.

Architectural Impact

• Positive: The Zod integration establishes a Single Source of Truth for runtime validation and static types.
• Negative: Mixing these changes into a "chore" PR undermines the stability of the main branch by bypassing focused review on the logic changes.

Recommendation

CHANGES REQUESTED.

1. Revert logic changes in context/webSocketReducer.ts and types/websocket.ts.
2. OR Update the PR title/description to reflect that this is a "Refactor: WebSocket Types and Reducer Optimization" and explicitly list the behavioral changes.
3. Fix the type assertions in socketManager.test.ts.

Review automatically published via RepoAuditor.

[arii]

Reviewed commit: 7e1bb3c30df85dc450f5dbebdb9e19f0a3a2eefc

This PR successfully addresses the goal of removing 'AI slop' comments, significantly improving code readability and conciseness across multiple files. The removal of redundant and self-evident comments aligns perfectly with the project's CODE_REVIEW_GUIDELINES.md on eliminating verbose code.

Strengths

• Reduced AI Slop: Numerous unnecessary comments have been removed from context/webSocketReducer.ts, hooks/useSpotifyWebPlayback.ts, tests/playwright/stale-tile.spec.ts, tests/unit/hooks/useSpotifyWebPlayback.test.ts, and tests/unit/socketManager.test.ts. This makes the code cleaner and more self-documenting.
• Improved HRM_UPDATE Logic: The refactoring of the HRM_UPDATE case in context/webSocketReducer.ts is a significant improvement. The new logic uses a Map for efficient merging of existing client-side data with the authoritative server payload, resulting in a more concise, readable, and potentially more performant update mechanism. This adheres to the 'Avoid Overly Complex Solutions' and 'Don't Repeat Yourself (DRY)' principles.
• Test File Relocation: The unit test for webSocketReducer was correctly moved from tests/unit/context/webSocketReducer.test.ts to tests/unit/webSocketReducer.test.ts, reflecting the logical grouping of tests.

Issues

No issues found. The changes are well-executed and enhance the codebase.

Verdict

✅ Verified that AI slop comments were removed and the webSocketReducer logic was refactored for clarity and efficiency. No regressions or new issues were introduced. Ready for approval.

Reviewed at commit: 7e1bb3c30df85dc450f5dbebdb9e19f0a3a2eefc

[arii]

@conflict-resolve

[arii]

@conflict-resolve

[github-actions]

⏳ Attempting to automatically resolve conflicts for branch refactor/remove-ai-slop-comments-15466379085910369930...

[github-actions]

❌ Error: Unable to automatically resolve all conflicts.
The following files have unresolved conflicts:

Please resolve these conflicts manually.

[arii]

🤖 AI Technical Audit

Code Review: PR #6653

This PR achieves its primary goal of removing "AI slop" comments and standardizing code, but it also includes significant refactoring of logic and tests that exceeds a simple "comment cleanup" scope. While most changes are improvements, there is a critical issue in the unit test mocking strategy that introduces network side effects.

⚠️ ANTI-AI-SLOP DIRECTIVES

1. OVERLY VERBOSE COMMENTS: ✅ Addressed. The PR successfully removed conversational comments in context/webSocketReducer.ts (e.g., "THE FIX: Immediately filter...") and hooks/useSpotifyWebPlayback.ts.
2. OVER-ENGINEERING: ✅ Reduced. The logic in webSocketReducer.ts was simplified from a verbose filter/map/forEach chain to a concise Map-based lookup.
3. DUPLICATE HOOKS/TYPES: ✅ Fixed. types/websocket.ts drastically reduces duplication by deriving TypeScript types directly from Zod schemas (z.infer), eliminating the risk of the interface and schema drifting apart.
4. CODE RATIO: ✅ Excellent. types/websocket.ts removed ~100 lines of redundant interface definitions. webSocketReducer.ts logic is compressed by ~50%.
5. STALE FEATURES: ✅ Verified. The deletion of tests/unit/context/webSocketReducer.test.ts is matched by the creation of tests/unit/webSocketReducer.test.ts.

📁 File-by-File Analysis

types/websocket.ts

• Improvement: Moving to Zod-inferred types is a major architectural win for Type Safety.
• Caution: Ensure PingMessageSchema is defined before it is used in the ClientCommandMessageSchema union. Zod schemas are variables, not hoisted types, so order matters. Reference errors will occur at runtime if the topological sort is incorrect.

context/webSocketReducer.ts

• Refactor: The logic change in HRM_UPDATE is functionally equivalent to the old code but cleaner. It correctly treats the server payload as the authoritative source of truth.

tests/unit/socketManager.test.ts

• ⛔️ CRITICAL PROBLEM: The new mock implementation extends the real WebSocket class.

  // PROBLEM: This attempts a real network connection during a UNIT test
  class MockWebSocket extends RealWebSocket {
    constructor(address: string) {
      super(address || 'ws://test') // <--- Triggers native connection logic
      // ...
    }
  }

  Why this is bad: Unit tests should never attempt real network I/O. Even if you suppress errors, super() invokes the underlying library's connection logic, potentially causing timeouts, unhandled rejections, or flaky tests in CI environments without internet access.

Summary

The cleanup is excellent, but the test refactor introduced a regression in testing best practices (Mocking). Fix the WebSocket mock to prevent network calls.

Review automatically published via RepoAuditor.

[arii]

🤖 AI Technical Audit

Deep Code Review: PR #6653

🚮 Anti-AI-Slop Directives

1. OVER-ENGINEERING (Test Mocking): In tests/unit/socketManager.test.ts, the new MockWebSocket class extends the real WebSocket class (super(address || 'ws://test')). This triggers actual network stack operations in the underlying node/C++ layer, relying on a suppressed error handler (this.on('error', ...)). This is risky for unit tests as it introduces asynchronous side effects and potential flakiness.
2. CODE RATIO (Reducer Tests): The new test file tests/unit/webSocketReducer.test.ts is significantly larger than the deleted one (270 lines vs 185 lines). While it uses a helper factory createMockUser, the setup for each test case remains verbose. We can tighten this.
3. STALE FEATURES (Scope Creep): The PR description focuses on "removing comments", but types/websocket.ts introduces a significant architectural change by integrating Zod for schema validation. While valuable, this is a feature addition/refactor, not just a cleanup.

---

File-by-File Analysis

context/webSocketReducer.ts

Assessment: Improved Complexity (O(N) vs O(N²)).

The refactor of the HRM_UPDATE case is excellent. By creating a Map of existing data and iterating only over the payload, you essentially switched from an O(N*M) operation to O(N). The comment replacement is also much more professional.

Best Practice Check:
The logic assumes the payload is the definitive list of all connected clients. If the server ever switches to sending "deltas" (only changed clients), this logic will incorrectly drop clients not in the current payload. Ensure the server contract guarantees full snapshots for HRM_UPDATE.

types/websocket.ts

Assessment: Significant Positive Architecture Change.

Moving to Zod for type definitions (z.infer<...>) is a strong move for runtime validation reliability.

Problem: Inconsistent Schema usage.
You defined SpotifyCommandSchema but SpotifyCommandMessageSchema seems to redefine the structure rather than fully composing it. Also, ServerMessage is not validated via Zod, only client messages are.

tests/unit/socketManager.test.ts

Problem: Hazardous Mocking Strategy.

Implementation Sample (Current):

class MockWebSocket extends RealWebSocket {
  constructor(address: string) {
    super(address || 'ws://test') // Triggers REAL connection attempt
    this.on('error', () => {})    // Suppresses the inevitable error
  }
}

Implementation Sample (Recommended):
Use a pure JavaScript mock that mimics the interface without inheriting the internal networking logic.

class MockWebSocket extends EventEmitter {
  readyState = 1;
  send = jest.fn();
  terminate = jest.fn();
  // ... explicitly define needed methods only
}

Automated Checks Correlation

All checks passed, confirming that the new Zod types and reducer logic are compatible with the existing codebase. The Unit Tests success suggests the ws mock works in the current environment, but it remains a fragility risk for the future.

Review automatically published via RepoAuditor.