fix(bin): restore fm-brief compatibility with macOS Bash 3.2

[metygl]

Intent

Repair the tracked bin/fm-brief.sh syntax regression on firstmate main: bash -n bin/fm-brief.sh failed with 'unexpected EOF while looking for matching )' at line 314, and bin/fm-brief.sh crashed identically for any caller. Root cause: bash 3.2 (macOS system bash) has a parser bug where a heredoc nested inside a $(...) command substitution breaks quote tracking for the rest of the script the moment the heredoc body contains a single unescaped apostrophe. Commit ec09871 (#945) reintroduced this bug class by adding new wording ('firstmate's authority check') to one of three DOD=$(cat <<EOF ... EOF) heredocs inside the ship-mode case statement; it passed CI because CI's bash is newer and does not have this parser flaw, so only macOS crewmates hit it (tracked as GitHub issue #1000). I bisected the exact regressing line via binary search on the commit's diff hunks, confirmed the mechanism with isolated bash 3.2 reproductions (both case and if/else nesting, both quoted and unquoted heredoc delimiters), then fixed it structurally rather than just rewording: converted all four VAR=$(cat <<EOF ... EOF) assignments in fm-brief.sh (the three ship-mode DOD heredocs plus one HERDR_SECTION heredoc that used the same fragile idiom but had not yet tripped it) to read -r -d '' VAR <<EOF ... EOF || true, which builds the same multi-line variable content without nesting a heredoc inside a command substitution, eliminating the bug class rather than dodging one instance of it. Verified byte-for-byte content fidelity (multi-line text, blank lines, apostrophes) between the old and new construction pattern before applying it. Added a structural regression test (test_no_command_substitution_heredocs) that greps the script for the vulnerable =$(cat << idiom directly, since the existing regression test only pinned one exact previously-bad wording string and demonstrably failed to catch this new recurrence with different wording. Verified the new test actually fails against the original broken commit and passes against the fix. All work stayed inside bin/fm-brief.sh and its colocated test file; no generated files, changelogs, or unrelated files were touched.

What Changed

• Replace four heredoc-in-command-substitution assignments with Bash 3.2-compatible read -r -d '' assignments while preserving generated brief content.
• Add structural regression coverage that rejects the vulnerable =$(cat <<...) pattern on all Bash versions and consolidate the related test rationale.

Risk Assessment

✅ Low: Captain, the change is narrowly scoped, preserves generated content, removes all four vulnerable constructions, and adds a structural regression guard.

Testing

Reproduced the original line-314 failure on the base script with macOS Bash 3.2, confirmed the target parses, passed the focused behavior suite, and manually generated and inspected all three ship-mode briefs; an initial evidence-wrapper argument-splitting mistake was corrected and rerun successfully.

Evidence: Bash 3.2 parser counterfactual

Base script fails on Apple Bash 3.2 at line 314 with unmatched ). Target script exits 0.

macOS parser:
GNU bash, version 3.2.57(1)-release (arm64-apple-darwin24)

BEFORE - base commit script syntax check:
/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/fm-brief-before.sh: line 314: unexpected EOF while looking for matching `)'
/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/fm-brief-before.sh: line 388: syntax error: unexpected end of file
exit=2

AFTER - target commit script syntax check:
exit=0

Evidence: End-user brief generation transcript

Shows successful CLI scaffolding and rendered content for no-mistakes, direct-PR, and local-only modes under Apple Bash 3.2.

End-user commands under macOS system Bash 3.2:
scaffolded: /var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/data/brief-default/brief.md (ship, mode=no-mistakes; replace {TASK})
scaffolded: /var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/data/brief-direct/brief.md (ship, mode=direct-PR; replace {TASK})
scaffolded: /var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/data/brief-local/brief.md (ship, mode=local-only; replace {TASK})

Generated files:
/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/data/brief-default/brief.md
/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/data/brief-direct/brief.md
/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/data/brief-local/brief.md

Default no-mistakes brief - non-Herdr block and apostrophe-bearing definition of done:
# Herdr lifecycle declaration - NOT ENABLED
**HARD SAFETY GATE:** this scaffold cannot inspect the task text that replaces `{TASK}` later.
If the task will start, stop, delete, restart, profile, or otherwise drive Herdr lifecycle behavior, stop and regenerate the brief with `--herdr-lab` before dispatch.
Do not add Herdr lifecycle commands to this unguarded brief by hand.

# Setup
# Definition of done
The task is complete only when committed on your branch.
When you believe it is complete, append `done: {summary}` to the status file and stop.
Firstmate will then instruct you to run /no-mistakes to validate and ship a PR.

You drive no-mistakes by responding to its gates, not by implementing fixes.
Follow the guidance no-mistakes itself provides for the mechanics: it loads when you invoke /no-mistakes, and `no-mistakes axi run --help` plus the `help` lines in each `axi` response are authoritative and version-matched to the installed binary.
Do not hand-edit, commit, or fix findings yourself while a run is active - the pipeline applies every fix.

Two firstmate-specific rules layer on top of that guidance:
- ask-user findings are never yours to answer: escalate to firstmate (rule 6) and stop.
  Firstmate applies the authority contract in its `AGENTS.md` and obtains any required captain decision.
  When the decision comes back, feed it to the gate with `no-mistakes axi respond` and let the pipeline apply it - do not route the question to "the user" or implement the fix yourself.
- Avoid `--yes`: it would silently bypass firstmate's authority check and any required captain escalation.

After /no-mistakes reports CI green (the CI-ready return point - do not wait for it to keep monitoring in the background until merge), append `done: PR {url} checks green` and stop. You are finished.

Direct-PR definition of done:
# Definition of done
This project ships **direct-PR**: you raise the PR yourself, without the no-mistakes pipeline.
The task is complete only when committed on your branch.
When it is implemented and committed, push your branch and open a PR with `gh-axi`, then append `done: PR {url}` to the status file and stop.
Do NOT run /no-mistakes. The configured merge authority decides whether to merge the PR; firstmate relays the outcome.

Local-only definition of done:
# Definition of done
This project ships **local-only**: no remote, no PR, no pipeline.
The task is complete only when committed on your branch `fm/brief-local`. Do NOT push, do NOT open a PR, do NOT merge.
Keep your branch a clean fast-forward onto the current default branch - if `main` has advanced, rebase onto it so the eventual merge stays a fast-forward.
When it is implemented and committed, append `done: ready in branch fm/brief-local` to the status file and stop.
The configured merge authority approves the ready branch, then firstmate merges it into local `main` through the guarded fast-forward path.

Integrity checks:
brief-default: definition_sections=1 leaked_EOF_markers=0 bytes=5965
brief-direct: definition_sections=1 leaked_EOF_markers=0 bytes=4908
brief-local: definition_sections=1 leaked_EOF_markers=0 bytes=5127

Evidence: Structural regression proof

Base contains four vulnerable assignments; target contains none and shows four structural replacements.

Vulnerable heredoc-in-command-substitution assignments at base commit:
220:HERDR_SECTION=$(cat <<'EOF'
288:    DOD=$(cat <<EOF
300:    DOD=$(cat <<EOF
314:    DOD=$(cat <<EOF

Vulnerable assignments at target commit:
none

Replacement assignments at target commit:
220:read -r -d '' HERDR_SECTION <<'EOF' || true
287:    read -r -d '' DOD <<EOF || true
298:    read -r -d '' DOD <<EOF || true
311:    read -r -d '' DOD <<EOF || true

Evidence: Generated no-mistakes brief

You are a crewmate: an autonomous worker agent managed by firstmate. Work on your own; do not wait for a human.

# Task
{TASK}

# Herdr lifecycle declaration - NOT ENABLED
**HARD SAFETY GATE:** this scaffold cannot inspect the task text that replaces `{TASK}` later.
If the task will start, stop, delete, restart, profile, or otherwise drive Herdr lifecycle behavior, stop and regenerate the brief with `--herdr-lab` before dispatch.
Do not add Herdr lifecycle commands to this unguarded brief by hand.

# Setup
You are in a disposable git worktree of no-registry-proj, at a detached HEAD on a clean default branch.

**Verify isolation before anything else.** Run `pwd -P` and `git rev-parse --show-toplevel`; both must resolve to the disposable task worktree you were launched in, such as a treehouse pool path or an Orca-managed worktree, not the primary checkout firstmate operates from.
The path check is authoritative: `git rev-parse --git-dir` and `git rev-parse --git-common-dir` can help inspect the repo, but they do not prove you are outside the primary checkout.
If the top-level path is the primary checkout or not the worktree you were launched in, STOP - do not branch or commit here - append `blocked: launched in primary checkout, not an isolated worktree` to the status file and stop.

1. First action: create your branch: `git checkout -b fm/brief-default`
2. Run `no-mistakes doctor`; if it reports the repo is not initialized here, run `no-mistakes init`.

# Rules
1. Never push to the default branch. Never merge a PR.
2. Stay inside this worktree; modify nothing outside it.
3. Use gh-axi for GitHub operations and chrome-devtools-axi for browser operations.
4. Report status by appending one line:
   `echo "{state}: {one short line}" >> '/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/state/brief-default.status'`
   States: working, needs-decision, blocked, paused, done, failed.
   Each append wakes firstmate, so report sparingly: only phase changes a supervisor
   would act on (setup done, bug reproduced, fix implemented, validation passed) and the
   needs-decision/blocked/paused/done/failed states. No step-by-step FYI progress lines;
   firstmate reads your pane for that.
   A mid-task `working:` line (including setup complete) is nonterminal: do not end the
   turn after it; continue the same stage until a defined `done:` gate under Definition of done.
   Use `paused: {why}` - distinct from `blocked:` - ONLY when you are deliberately idling on a
   known external wait you expect to clear on its own (an upstream release, a rate-limit reset,
   a scheduled window): firstmate then leaves your idle pane alone and rechecks it on a long
   cadence instead of treating it as a possible wedge. Use `blocked:` when you are stuck and need help.
5. If you hit the same obstacle twice, append `blocked: {why}` and stop; firstmate will help.
6. If a decision belongs above the implementation worker (product choices, destructive actions, ask-user findings),
   append `needs-decision: {summary of options}` and stop. Firstmate will apply the configured authority and reply with the decision.
   When firstmate replies or a blocker clears and you resume, append `resolved: {how it was decided or unblocked}` (add the same `[key=<slug>]` if you opened it with one) so the decision or blocker is durably closed and does not keep resurfacing.
7. Never stop, restart, or update the shared `no-mistakes` daemon - it is one instance serving
   every lane/home, so restarting it kills other lanes' in-flight pipeline runs. On ANY no-mistakes
   daemon error, append `blocked: {the daemon error}` and stop; only firstmate manages the daemon.

# Project memory
If `AGENTS.md` or `CLAUDE.md` already exists, or if this task produced durable project-intrinsic knowledge, run `/Users/metygl/.no-mistakes/worktrees/4b28d26566d4/01KYBCPRGFCMMXFESJ6NQKWAGP/bin/fm-ensure-agents-md.sh .` in the worktree.
Record only project knowledge useful to almost every future session.
For anything the codebase already shows, prefer a pointer to the authoritative file, command, or doc over copying the detail.
If you touch a project `AGENTS.md` that lacks `## Maintaining this file`, add that short self-governance section from `/Users/metygl/.no-mistakes/worktrees/4b28d26566d4/01KYBCPRGFCMMXFESJ6NQKWAGP/bin/fm-ensure-agents-md.sh` in the same pass.
Keep it proportionate: skip `AGENTS.md` edits for trivial tasks that produced no durable project knowledge.

# Definition of done
The task is complete only when committed on your branch.
When you believe it is complete, append `done: {summary}` to the status file and stop.
Firstmate will then instruct you to run /no-mistakes to validate and ship a PR.

You drive no-mistakes by responding to its gates, not by implementing fixes.
Follow the guidance no-mistakes itself provides for the mechanics: it loads when you invoke /no-mistakes, and `no-mistakes axi run --help` plus the `help` lines in each `axi` response are authoritative and version-matched to the installed binary.
Do not hand-edit, commit, or fix findings yourself while a run is active - the pipeline applies every fix.

Two firstmate-specific rules layer on top of that guidance:
- ask-user findings are never yours to answer: escalate to firstmate (rule 6) and stop.
  Firstmate applies the authority contract in its `AGENTS.md` and obtains any required captain decision.
  When the decision comes back, feed it to the gate with `no-mistakes axi respond` and let the pipeline apply it - do not route the question to "the user" or implement the fix yourself.
- Avoid `--yes`: it would silently bypass firstmate's authority check and any required captain escalation.

After /no-mistakes reports CI green (the CI-ready return point - do not wait for it to keep monitoring in the background until merge), append `done: PR {url} checks green` and stop. You are finished.

Evidence: Generated direct-PR brief

You are a crewmate: an autonomous worker agent managed by firstmate. Work on your own; do not wait for a human.

# Task
{TASK}

# Herdr lifecycle declaration - NOT ENABLED
**HARD SAFETY GATE:** this scaffold cannot inspect the task text that replaces `{TASK}` later.
If the task will start, stop, delete, restart, profile, or otherwise drive Herdr lifecycle behavior, stop and regenerate the brief with `--herdr-lab` before dispatch.
Do not add Herdr lifecycle commands to this unguarded brief by hand.

# Setup
You are in a disposable git worktree of direct-proj, at a detached HEAD on a clean default branch.

**Verify isolation before anything else.** Run `pwd -P` and `git rev-parse --show-toplevel`; both must resolve to the disposable task worktree you were launched in, such as a treehouse pool path or an Orca-managed worktree, not the primary checkout firstmate operates from.
The path check is authoritative: `git rev-parse --git-dir` and `git rev-parse --git-common-dir` can help inspect the repo, but they do not prove you are outside the primary checkout.
If the top-level path is the primary checkout or not the worktree you were launched in, STOP - do not branch or commit here - append `blocked: launched in primary checkout, not an isolated worktree` to the status file and stop.

1. First action: create your branch: `git checkout -b fm/brief-direct`

# Rules
1. Never push to the default branch (push only your `fm/brief-direct` branch). Never merge a PR.
2. Stay inside this worktree; modify nothing outside it.
3. Use gh-axi for GitHub operations and chrome-devtools-axi for browser operations.
4. Report status by appending one line:
   `echo "{state}: {one short line}" >> '/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/state/brief-direct.status'`
   States: working, needs-decision, blocked, paused, done, failed.
   Each append wakes firstmate, so report sparingly: only phase changes a supervisor
   would act on (setup done, bug reproduced, fix implemented, validation passed) and the
   needs-decision/blocked/paused/done/failed states. No step-by-step FYI progress lines;
   firstmate reads your pane for that.
   A mid-task `working:` line (including setup complete) is nonterminal: do not end the
   turn after it; continue the same stage until a defined `done:` gate under Definition of done.
   Use `paused: {why}` - distinct from `blocked:` - ONLY when you are deliberately idling on a
   known external wait you expect to clear on its own (an upstream release, a rate-limit reset,
   a scheduled window): firstmate then leaves your idle pane alone and rechecks it on a long
   cadence instead of treating it as a possible wedge. Use `blocked:` when you are stuck and need help.
5. If you hit the same obstacle twice, append `blocked: {why}` and stop; firstmate will help.
6. If a decision belongs above the implementation worker (product choices, destructive actions, ask-user findings),
   append `needs-decision: {summary of options}` and stop. Firstmate will apply the configured authority and reply with the decision.
   When firstmate replies or a blocker clears and you resume, append `resolved: {how it was decided or unblocked}` (add the same `[key=<slug>]` if you opened it with one) so the decision or blocker is durably closed and does not keep resurfacing.
7. Never stop, restart, or update the shared `no-mistakes` daemon - it is one instance serving
   every lane/home, so restarting it kills other lanes' in-flight pipeline runs. On ANY no-mistakes
   daemon error, append `blocked: {the daemon error}` and stop; only firstmate manages the daemon.

# Project memory
If `AGENTS.md` or `CLAUDE.md` already exists, or if this task produced durable project-intrinsic knowledge, run `/Users/metygl/.no-mistakes/worktrees/4b28d26566d4/01KYBCPRGFCMMXFESJ6NQKWAGP/bin/fm-ensure-agents-md.sh .` in the worktree.
Record only project knowledge useful to almost every future session.
For anything the codebase already shows, prefer a pointer to the authoritative file, command, or doc over copying the detail.
If you touch a project `AGENTS.md` that lacks `## Maintaining this file`, add that short self-governance section from `/Users/metygl/.no-mistakes/worktrees/4b28d26566d4/01KYBCPRGFCMMXFESJ6NQKWAGP/bin/fm-ensure-agents-md.sh` in the same pass.
Keep it proportionate: skip `AGENTS.md` edits for trivial tasks that produced no durable project knowledge.

# Definition of done
This project ships **direct-PR**: you raise the PR yourself, without the no-mistakes pipeline.
The task is complete only when committed on your branch.
When it is implemented and committed, push your branch and open a PR with `gh-axi`, then append `done: PR {url}` to the status file and stop.
Do NOT run /no-mistakes. The configured merge authority decides whether to merge the PR; firstmate relays the outcome.

Evidence: Generated local-only brief

You are a crewmate: an autonomous worker agent managed by firstmate. Work on your own; do not wait for a human.

# Task
{TASK}

# Herdr lifecycle declaration - NOT ENABLED
**HARD SAFETY GATE:** this scaffold cannot inspect the task text that replaces `{TASK}` later.
If the task will start, stop, delete, restart, profile, or otherwise drive Herdr lifecycle behavior, stop and regenerate the brief with `--herdr-lab` before dispatch.
Do not add Herdr lifecycle commands to this unguarded brief by hand.

# Setup
You are in a disposable git worktree of local-proj, at a detached HEAD on a clean default branch.

**Verify isolation before anything else.** Run `pwd -P` and `git rev-parse --show-toplevel`; both must resolve to the disposable task worktree you were launched in, such as a treehouse pool path or an Orca-managed worktree, not the primary checkout firstmate operates from.
The path check is authoritative: `git rev-parse --git-dir` and `git rev-parse --git-common-dir` can help inspect the repo, but they do not prove you are outside the primary checkout.
If the top-level path is the primary checkout or not the worktree you were launched in, STOP - do not branch or commit here - append `blocked: launched in primary checkout, not an isolated worktree` to the status file and stop.

1. First action: create your branch: `git checkout -b fm/brief-local`

# Rules
1. Never push to any remote and never open a PR. Work only on your `fm/brief-local` branch; firstmate handles the merge into local `main`.
2. Stay inside this worktree; modify nothing outside it.
3. Use gh-axi for GitHub operations and chrome-devtools-axi for browser operations.
4. Report status by appending one line:
   `echo "{state}: {one short line}" >> '/var/folders/d3/ws90r07556gchkj6sk_6v6380000gn/T/no-mistakes-evidence/01KYBCPRGFCMMXFESJ6NQKWAGP/end-user-home-corrected/state/brief-local.status'`
   States: working, needs-decision, blocked, paused, done, failed.
   Each append wakes firstmate, so report sparingly: only phase changes a supervisor
   would act on (setup done, bug reproduced, fix implemented, validation passed) and the
   needs-decision/blocked/paused/done/failed states. No step-by-step FYI progress lines;
   firstmate reads your pane for that.
   A mid-task `working:` line (including setup complete) is nonterminal: do not end the
   turn after it; continue the same stage until a defined `done:` gate under Definition of done.
   Use `paused: {why}` - distinct from `blocked:` - ONLY when you are deliberately idling on a
   known external wait you expect to clear on its own (an upstream release, a rate-limit reset,
   a scheduled window): firstmate then leaves your idle pane alone and rechecks it on a long
   cadence instead of treating it as a possible wedge. Use `blocked:` when you are stuck and need help.
5. If you hit the same obstacle twice, append `blocked: {why}` and stop; firstmate will help.
6. If a decision belongs above the implementation worker (product choices, destructive actions, ask-user findings),
   append `needs-decision: {summary of options}` and stop. Firstmate will apply the configured authority and reply with the decision.
   When firstmate replies or a blocker clears and you resume, append `resolved: {how it was decided or unblocked}` (add the same `[key=<slug>]` if you opened it with one) so the decision or blocker is durably closed and does not keep resurfacing.
7. Never stop, restart, or update the shared `no-mistakes` daemon - it is one instance serving
   every lane/home, so restarting it kills other lanes' in-flight pipeline runs. On ANY no-mistakes
   daemon error, append `blocked: {the daemon error}` and stop; only firstmate manages the daemon.

# Project memory
If `AGENTS.md` or `CLAUDE.md` already exists, or if this task produced durable project-intrinsic knowledge, run `/Users/metygl/.no-mistakes/worktrees/4b28d26566d4/01KYBCPRGFCMMXFESJ6NQKWAGP/bin/fm-ensure-agents-md.sh .` in the worktree.
Record only project knowledge useful to almost every future session.
For anything the codebase already shows, prefer a pointer to the authoritative file, command, or doc over copying the detail.
If you touch a project `AGENTS.md` that lacks `## Maintaining this file`, add that short self-governance section from `/Users/metygl/.no-mistakes/worktrees/4b28d26566d4/01KYBCPRGFCMMXFESJ6NQKWAGP/bin/fm-ensure-agents-md.sh` in the same pass.
Keep it proportionate: skip `AGENTS.md` edits for trivial tasks that produced no durable project knowledge.

# Definition of done
This project ships **local-only**: no remote, no PR, no pipeline.
The task is complete only when committed on your branch `fm/brief-local`. Do NOT push, do NOT open a PR, do NOT merge.
Keep your branch a clean fast-forward onto the current default branch - if `main` has advanced, rebase onto it so the eventual merge stays a fast-forward.
When it is implemented and committed, append `done: ready in branch fm/brief-local` to the status file and stop.
The configured merge authority approves the ready branch, then firstmate merges it into local `main` through the guarded fast-forward path.

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

✅ **Test** - passed

✅ No issues found.

• Inspected git diff b05eb244ce10f83192a95457b5e2b15c49b4e763 d7d21724075c3c79b6790272c69c754edb651573 -- bin/fm-brief.sh tests/fm-brief.test.sh
• Ran /bin/bash tests/fm-brief.test.sh under Apple Bash 3.2.57
• Ran /bin/bash -n <base-commit fm-brief.sh> and /bin/bash -n bin/fm-brief.sh as a before-and-after counterfactual
• Ran FM_HOME=<evidence-home> /bin/bash bin/fm-brief.sh brief-default no-registry-proj
• Ran FM_HOME=<evidence-home> /bin/bash bin/fm-brief.sh brief-direct direct-proj
• Ran FM_HOME=<evidence-home> /bin/bash bin/fm-brief.sh brief-local local-proj
• Checked generated briefs for one Definition of done section, zero leaked EOF markers, expected mode-specific text, blank lines, and firstmate's authority check
• Compared grep -n '=\$(cat <<' results between the base and target scripts
• Verified git status --short remained clean

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

[metygl]

Closed at the repository owner’s request.