Process completed with exit code 1.

Missing `#[Override]` attribute on overriding method `App\Web\Blog\BlogIndexer::index`. The `#[Override]` attribute clarifies intent and prevents accidental signature mismatches. Help: Add `#[Override]` attribute to method declaration.

Missing `#[Override]` attribute on overriding method `App\Highlight\Patterns\TempestViewCommentPattern::getTokenType`. The `#[Override]` attribute clarifies intent and prevents accidental signature mismatches. Help: Add `#[Override]` attribute to method declaration.

Missing `#[Override]` attribute on overriding method `App\Web\CommandPalette\CommandIndexer::index`. The `#[Override]` attribute clarifies intent and prevents accidental signature mismatches. Help: Add `#[Override]` attribute to method declaration.

Missing `#[Override]` attribute on overriding method `App\Web\Community\CommunityPostIndexer::index`. The `#[Override]` attribute clarifies intent and prevents accidental signature mismatches. Help: Add `#[Override]` attribute to method declaration.

Missing `#[Override]` attribute on overriding method `App\Web\Documentation\DocumentationIndexer::index`. The `#[Override]` attribute clarifies intent and prevents accidental signature mismatches. Help: Add `#[Override]` attribute to method declaration.

Missing `#[Override]` attribute on overriding method `App\Web\CommandPalette\IndexerDiscovery::apply`. The `#[Override]` attribute clarifies intent and prevents accidental signature mismatches. Help: Add `#[Override]` attribute to method declaration.

Missing `#[Override]` attribute on overriding method `App\Web\CommandPalette\IndexerDiscovery::discover`. The `#[Override]` attribute clarifies intent and prevents accidental signature mismatches. Help: Add `#[Override]` attribute to method declaration.

Literal argument `'<x-icon :name="$name" class="alert-icon" />'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '<x-icon :name="$name" class="alert-icon" />')` instead of `function_name('<x-icon :name="$name" class="alert-icon" />')`.

Literal argument `'</span>'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '</span>')` instead of `function_name('</span>')`.

Literal argument `'<span class="hl-console-strong">'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '<span class="hl-console-strong">')` instead of `function_name('<span class="hl-console-strong">')`.

Literal argument `'%s%s%s'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '%s%s%s')` instead of `function_name('%s%s%s')`.

Literal argument `'</span>'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '</span>')` instead of `function_name('</span>')`.

Literal argument `'<span class="hl-console-question">'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '<span class="hl-console-question">')` instead of `function_name('<span class="hl-console-question">')`.

Literal argument `'%s%s%s'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '%s%s%s')` instead of `function_name('%s%s%s')`.

Literal argument `'{(twitter|x|bluesky|bsky|gh|github):(.+?)(?:,(.+?))?}'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '{(twitter|x|bluesky|bsky|gh|github):(.+?)(?:,(.+?))?}')` instead of `function_name('{(twitter|x|bluesky|bsky|gh|github):(.+?)(?:,(.+?))?}')`.

Literal argument `'/<h3.*>.*<a.*href="(?<h3uri>.*?)".*?<\/span>(?<h3title>.*)<\/a><\/h3>/'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '/<h3.*>.*<a.*href="(?<h3uri>.*?)".*?<\/span>(?<h3title>.*)<\/a><\/h3>/')` instead of `function_name('/<h3.*>.*<a.*href="(?<h3uri>.*?)".*?<\/span>(?<h3title>.*)<\/a><\/h3>/')`.

Literal argument `'/<h2.*>.*<a.*href="(?<uri>.*?)".*?<\/span>(?<title>.*)<\/a><\/h2>/'` should be passed as a named argument for clarity. Using named arguments for literals, especially booleans, numbers, or `null`, makes the function/method call more self-documenting by clarifying the purpose of the value. Help: Consider changing the call to `function_name(literal: '/<h2.*>.*<a.*href="(?<uri>.*?)".*?<\/span>(?<title>.*)<\/a><\/h2>/')` instead of `function_name('/<h2.*>.*<a.*href="(?<uri>.*?)".*?<\/span>(?<title>.*)<\/a><\/h2>/')`.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.

Parameter `$b` is never used. This parameter is declared but not used within the arrow function. Help: Consider prefixing the parameter with an underscore (`_`) to indicate that it is intentionally unused, or remove it if it is not needed.

Parameter `$clock` is never used. This parameter is declared but not used within the method. Help: Consider prefixing the parameter with an underscore (`_`) to indicate that it is intentionally unused, or remove it if it is not needed.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.

Unbraced variable in string interpolation Using curly braces around variables in interpolated strings improves readability and prevents potential parsing issues. Help: Wrap the variable in curly braces, e.g., `{$variable}`.