[brettheap]

Lane: openreposhape-5 (openRepoShape-5)
Claim: #695 (comment)

The family docs now say what family.py init, make siblings and the members/ directory do since #488, #578 and #574. Base: 8062810d. Head: c42286de: the work (73fa3ff4) and one commit for the review's nit on L20.

Fix round: main merged in (2026-10-17)

The branch now holds origin/main at 24a977c0, through one merge commit, 75e35f14. No other commit was added, and nothing was rebased or amended.

What failed

Since #682 landed (dc7d3fbb), git merge-tree --write-tree HEAD origin/main against c42286de stopped on one line of docs/handbook.html:

Auto-merging docs/handbook.html
CONFLICT (content): Merge conflict in docs/handbook.html

It is the families section's marker, <!-- reads README.md § Families: ... blob <hash> -->. #682 changed a sentence of README § Families, so main's marker is b3d19092.... This PR changed other sentences of the same section, so its marker is 0364c579.... Git saw one line changed two ways. Lane 2's note on #738 (2026-10-17T12:47:17Z) named the same line. I reproduced the conflict on the head I started from, then merged by hand.

The fix

The merged README § Families is neither side's text, so the marker takes its fingerprint, 82d7f8087b9ee4d097d33e15fbfe5ae754a04a79. I computed it with tests/test_repo_hygiene.py's own readme_fingerprint over the merged README.md. It is the value lane 2's note gave, and it did not move when main moved on to 24a977c0.

marker value	where it came from	handbook outline test
b3d19092...	main's side	fails: "has moved since the page read it"
0364c579...	this PR's side	fails, same message
82d7f808...	the merged README § Families	passes

I re-read both sides before taking the value:

• Main's side brought one sentence into README § Families (line 955, "make bootstrap reports and skips one it lacks a credential for."), and bootstrap.py and validate-family.py: a member no credential would check out fails the family bootstrap, every row's gitlink is asked before any checkout, and --no-members prints the case-variant move (#648) #682 had already put the matching sentence on the page.
• This PR's side is its own 55 README lines and 27 handbook lines in that section, which merged clean.
• Both sides' sentences stand in the merged README and in the page.

Did the merge change README or handbook text beyond the conflict line?

No. I compared each changed file's diff against the parent that did not make it:

• README.md: the merge against origin/main shows exactly this PR's own change, and the merge against c42286de shows exactly main's own change since 8062810d (one line, bootstrap.py and validate-family.py: a member no credential would check out fails the family bootstrap, every row's gitlink is asked before any checkout, and --no-members prints the case-variant move (#648) #682's). No line differs.
• AGENTS.md: the same two comparisons, no line differs.
• docs/handbook.html: the same two comparisons differ in the marker line only, in both directions.
• README's handbook markers (23 on the page) and README's line cap are untouched. tests/test_repo_hygiene.py passes with the cap and the markers as they are.

This PR still lands only in lane 3's README turn. If another README PR changes § Families first, the marker moves again, and the hygiene test names it.

Tests

All on 75e35f14, through the gh stub, with a bogus token and an empty GH_CONFIG_DIR.

run	files	result
core	test_readme_sections.py, test_family_docs_one_spelling.py (the one test file this PR changes), test_repo_hygiene.py, test_agents_md_codes.py, test_cli_reference.py	240 passed
handbook readers	test_readme_windows_quoting_sentence.py, test_setup_by_hand_commands.py, test_update_add_codes_documented.py	20 passed
family-root templates	test_pinned_copy_text.py, test_template_values_single_pass.py, test_family_init_values.py, test_family_init_landing.py, test_siblings_family_name.py, test_family_makefile_siblings.py, test_family_siblings_placement.py	582 passed, 19 skipped
bootstrap (main's new files, over the template this PR reworded)	test_bootstrap_spelling.py, test_bootstrap_without_git.py, test_bootstrap_leg_moves.py	251 passed

Mutants

This round adds no test and no code, so its one hunk is the marker value. Each mutant changes that value in a shared scratch clone at 75e35f14 and runs tests/test_repo_hygiene.py::test_the_handbook_follows_the_readmes_outline:

mutant	result
none (control)	1 passed
main's marker b3d19092...	1 failed
this PR's marker 0364c579...	1 failed
the right marker with its last digit changed	1 failed
the unresolved conflict block (<<<<<<<, both lines, >>>>>>>)	1 failed

Merge checks

• git merge-tree --write-tree HEAD origin/main is clean at 24a977c0.
• Main moved to 40e678e6 (siblings.py: the printed move runs as typed past a taken staging name and names a dangling link to move aside first, a NUL or lone surrogate in project: or url is a finding, .gitmodules is read as git reads it, the warning's prose is spelled, and a tag-only branch is named (#690) #805, templates/family-root/scripts/siblings.py and tests/test_siblings_inputs.py) after this merge. It touches no README, handbook or AGENTS text, and the merge-tree against it is clean.
• Lane 2's family-root README.md and AGENTS-shape.md, and AGENTS.md: the holder's docs say its parent folder is named EXACTLY after its repository, case included, on every disk, and the never to hand-edit the members: block names the row repair validate-family.py asks for, whose commit is the person's #822 is stacked on this PR. Its reviewer found it merges clean with this PR landed at the same marker value.

What changed

1. The --into sentence (README.md § Families and the handbook). It gave the default, "the directory you are standing in", and not that init refuses that default inside a checkout of this standard. It now says so and names the code: (the directory you are standing in, by default; refused inside a checkout of this standard, \family-landing-in-standard`)`. AGENTS.md already said it.
2. The make siblings paragraph (README.md § Families and the handbook). It said make siblings "WARNS and prints the exact mv". Since siblings.py and family.py: make siblings asks about the family folder before it clones, clones each member on its tracking branch, and family.py siblings runs the holder's own copy (#543) #578 it also clones nothing until the mv is run, so the next run clones each member once, and a link of the family's name beside the folder passes. It now says that. Lane 3's two Tracking: shape-doctor.py, reporting a repository's compliance #460 sentences ride in it (L20, L21, which lane 3 marked -> #695):
   • the folder must be named EXACTLY after its repository, case included, on every disk;
   • for a holder at ~/projects/InkRouter the move makes the family folder ~/InkRouter, beside ~/projects, and the holder ~/InkRouter/InkRouter, not ~/projects/InkRouter/InkRouter.
     I wrote L20 with the paths spelled out. Lane 3's wording was "beside that folder's parent", which two readings can take. My first wording, "beside that folder, not inside it", still left one: the thing beside ~/projects is the family folder, not the holder (rv695 N1). The printed move for that holder is mv ~/projects/InkRouter ~/InkRouter.holder, mkdir -p ~/InkRouter, mv ~/InkRouter.holder ~/InkRouter/InkRouter (probe below, and test_family_siblings_placement.py pins it).
3. The one-spelling rule for members/. One sentence, the same words in five places: AGENTS.md (family item 2), README.md § Families, the handbook, the holder's README and the holder's AGENTS-shape.md:

   A holder keeps members/ in ONE spelling on every disk: add refuses family-members-dir-variant (member-path-taken for a variant of the member's own path) until a human renames what sits under another spelling.

Pinned copy: every holder re-pins

templates/family-root/AGENTS-shape.md changes by that one sentence. It is in FAMILY_COPIED_VERBATIM, so every holder reads upstream-changed for it on its next update-shape.py check. The issue's third line names it, and lane 3 asked that it ride with the next pinned-file edit. It can share the one v1.1.0 shape bump with the bootstrap fix. templates/family-root/README.md is templated and not pinned: an existing holder keeps its own README.

Caps: neither is raised

• README.md is 1458 lines, one under its cap of 1459 (1422 + 5 + 22 + 10 in tests/readme-cap.d/); it was 1459 at 73fa3ff4. The brief said 1449; that is the cap before README.md and the handbook: say that a source's own single-repository.yaml record arrives as leg: drop, that the adopted Makefile's CONTRACTS_DIR follows the spec leg's mount, and that a second setup run is refused at the plan, so the three sentences #566, #572 and #573 left false or incomplete are true of main (#606) #627 landed. AGENTS.md is 492, its cap.
• The new words come to about nine README lines and three AGENTS.md lines. I fitted them by cutting wording that is stated elsewhere. If you would rather keep the cut sentences, the alternative is a tests/readme-cap.d/695.txt of about +8, which needs Brett's word. What I cut:
  • README § Families:
    • the aside "the same lands-where-you-were-standing rule projects have";
    • four rewordings that lose no meaning:
      • the intro of "Use a family when the parts deploy separately": "folding them into one assembly root would give them one gate, one release and one pin, which is the opposite of what 'deploy separately' means" is now "one assembly root would give them one gate, one release and one pin, the opposite of 'deploy separately'";
      • "--work-dir remains the override" is now "--work-dir is the override";
      • "The doubled name is kept on purpose" is now "The doubled name is on purpose";
      • "family.yaml is what tells the two apart" is now "family.yaml tells the two apart";
    • the caption "Eight services, each its own project, one holder:" under "The InkRouter example" (the section's intro and the block under it say it; this is the one line cut to make room for the L20 rewording, and the handbook keeps its caption);
    • the tool's rationale after "Nothing ever moves a checkout" (the shell, the editor, the agent lanes, "an act by surprise"); it stays in the handbook, the holder's README and the tool's own output, and README keeps the reason that matters (a linked worktree's .git file carries an absolute path);
    • ", not merely a repository at the right commit";
    • the private-legs reason in the make bootstrap paragraph;
    • "to a policy two live projects already carry a copy of" in the naming paragraph.
  • AGENTS.md:
    • the converse in the family intro ("one project is what parts that ship together already are"; README keeps it);
    • the sentence "bump takes the same repeatable --trailer" in family item 3 (stated in "Advancing a leg" step 6 and in the holder's AGENTS-shape.md);
    • "Do not pass --yes on your own initiative" in "Updating" step 2, now "Never pass --yes yourself", the words test_repo_hygiene.py requires elsewhere in the file.
• The handbook marker for README § Families is recomputed with readme_segments / readme_fingerprint: 89ef0ab5ec88... to 0364c5794c46... (it was dc85a9260a67... at 73fa3ff4, before the L20 rewording and the caption cut). No other README section changed, so no other marker moves.

Tests

New file tests/test_family_docs_one_spelling.py, 17 tests: the one-spelling sentence in each of the five docs, the two codes held as strings by scripts/family.py, and the --into, make siblings, "named EXACTLY" and "straight in a folder" sentences in README and the handbook, plus the old "WARNS and prints" sentence gone from both. The handbook is read as the text a browser shows (<code> as backticks).

• On base 8062810d (the file copied in): 15 failed, 2 passed. The two that pass are the code-exists checks.
• On the head c42286de, after the L20 rewording: test_repo_hygiene.py, test_readme_sections.py, test_agents_md_codes.py and the new file: 217 passed in 3.37s. The new file's STRAIGHT_IN_A_FOLDER is in the new README and not in the old one.
• Before that, the targeted runs, each at 8062810d plus the working tree that was then the head (73fa3ff4):
  • test_repo_hygiene.py, test_readme_sections.py, test_agents_md_codes.py, test_cli_reference.py, test_readme_windows_quoting_sentence.py, test_setup_by_hand_commands.py, test_update_add_codes_documented.py and the new file: 253 passed.
  • Fifteen files that read AGENTS.md, the holder's docs or the refusals (test_family_init_landing, test_siblings_family_name, test_family_switch_branch_exists, test_family_tracking_branch, test_template_text_placeholders, test_template_values_single_pass, test_template_quoted_values, test_free_plan_hint, test_doctor_recorded_answers, test_update_shape_add, test_update_shape_header_comments, test_family_add_refusals, test_family_members_case_variants, test_family_member_path, test_doctor_legs_members_next): 987 passed.
  • Eight files: test_adopt_plan, test_adopt_github_exits, test_adopt_late_failure, test_setup_project_py, test_family, test_family_siblings_placement, test_family_makefile_siblings, test_park_resume_targets: 598 passed, 1 skipped (SHAPE_MEDXEHR_CLONE unset: a plan test needs a read-only clone of MedxSoft/MedxEHR, a cloud tool).
  • test_update_shape.py -k "shape_line or stale_readme or check_says_what_apply or readme_with_no_shape": 7 passed (the tests that read the holder README's last line). The rest of test_update_shape.py and test_shape_doctor.py were not run: they copy the family-root tree and match none of the lines I changed (git grep of the changed sentences under tests/ finds nothing), and a first run of them crawled under a load of 90-100 on the machine.
• The full suite was not run, as the brief says.

Reproduction

• Row 1, on base: from a checkout of the standard, python3 scripts/family.py init --org Acme --family Orbit --dry-run ends REFUSED family-landing-in-standard ... Remediation: pass \--into ..``. The README sentence did not say it would; it now does.
• Row 2, on head: parent_folder_warning of the holder's siblings.py for a holder at <t>/home/projects/InkRouter prints NOTHING WAS CLONED and the move mv .../projects/InkRouter .../InkRouter.holder, mkdir -p .../InkRouter, mv .../InkRouter.holder .../InkRouter/InkRouter. For a folder named inkrouter on Linux it stops the same way: the name test is exact on every disk.
• Row 3: the refusals the sentence names are the ones test_family_members_case_variants.py and test_family_add_refusals.py drive (60 + 65 tests, passed above).
• No row needs real GitHub or a cloud tool.

Mutation probes

My own run did not happen: a usage checkpoint stopped it before it began. The reviewer (rv695) ran 30 mutants against 73fa3ff4 in a throwaway clone and all 30 were killed: five places, four mutants each for the one-spelling sentence, and five each for the README and the handbook sentences. The L20 sentence has changed since, and STRAIGHT_IN_A_FOLDER with it; no mutant was run on the new words. What the guards cover there: the sentence has a parametrized case per doc, so reverting it fails that case, and a reverted README hunk leaves the handbook marker stale.

Merge checks (git merge-tree --write-tree HEAD <ref>, at c42286de)

• origin/main 55c6ba7d (it moved past 2fac9790 by shape-doctor.py: submodule_config and gitmodules_entry read a holder's .gitmodules through one git config -z --list, so a section name holding a space or a byte that is not UTF-8, or a url holding NEL or U+2028, gives the doctor the mount url git and make siblings use, under any locale (#668) #700): clean. rv695 found 73fa3ff4 clean against 2fac9790.
• README, AGENTS.md, docs/cli.md and the handbook: pipx install openreposhape is the second way in and the first on native Windows, git-filter-repo is installed in install.sh's order and never with a bare pip install, and a first draft of the v1.1.0 release notes (#563) #630 (lane 3), head 6fd33a93: clean. It merged main de926142, and its handbook conflicts at the three markers are gone. On the merged tree README.md is 1472 lines and AGENTS.md 494 (counted here; rv695 found them under README, AGENTS.md, docs/cli.md and the handbook: pipx install openreposhape is the second way in and the first on native Windows, git-filter-repo is installed in install.sh's order and never with a bare pip install, and a first draft of the v1.1.0 release notes (#563) #630's own ledger at 73fa3ff4).
• bootstrap.py and validate-family.py: a member no credential would check out fails the family bootstrap, every row's gitlink is asked before any checkout, and --no-members prints the case-variant move (#648) #682 (lane 5), head 8b39cd19: conflicts at one line, the handbook marker for README § Families (0364c5794c46... here, c40baa828dca... there). README.md and the rest of the handbook merge clean, and the merged paragraph reads correctly, because both PRs change that section. Whichever lands second recomputes the marker from the merged README: on this head plus bootstrap.py and validate-family.py: a member no credential would check out fails the family bootstrap, every row's gitlink is asked before any checkout, and --no-members prints the case-variant move (#648) #682 the recomputed value is da54c8ec2665... (computed with readme_fingerprint, not test-run).
• I dropped the earlier list of clean PRs: it was taken against older heads, and several of them have landed.

For lane 3: one sentence for the v1.1.0 release notes

(Brett Heap, 2026-10-16T13:36:23Z, on #459 line 141: "document it in the v1.1.0 release notes". docs/release-notes/v1.1.0.md exists only on #630, so this PR does not create it.)

A holder made with --family X --name Y before #642 (the fix for #629) keeps cd Y in its own README, and update-shape.py apply never re-renders a README, so change that one line by hand to cd X: the holder's directory is named after its repository, X, never after the display name.

Such a README also shows Y in its layout block and its doubled-name sentence, as prose; only the cd line fails when run.

Left out

• The holder's README does not get lane 3's L20 and L21: lane 3 asked for them in the README paragraph, and the holder's README already names the folder after the repository.
• Checklist candidate, not for this PR (rv695 N6): the holder's own docs say the folder is "named after the family" (templates/family-root/README.md:73, templates/family-root/AGENTS-shape.md:99) and not "EXACTLY, case included", which the standard's README and handbook now say and siblings.py tests (folder.name == family). Lane 3 asked for L21 only in the standard's README paragraph, so it is not owed here; it could ride in the same re-pin.

Closes #695

🤖 Generated with Claude Code

Summary by Sourcery

Update family documentation and validation tests to accurately describe initialization refusals, sibling cloning behavior, and the required members/ spelling.

Enhancements:

• Align family documentation with the current behavior of init and make siblings, including their refusal conditions and cloning workflow.
• Document the required single spelling of members/ and the associated refusal codes across standard and generated family documentation.
• Keep the handbook’s README section fingerprint synchronized after the documentation updates.

Documentation:

• Clarify family initialization placement, sibling directory naming and relocation guidance, and the members/ naming rule across README, handbook, AGENTS.md, and family-root templates.

Tests:

• Add documentation consistency tests covering the five copies of the members/ rule, refusal codes, initialization behavior, and sibling placement and cloning guidance.

[brettheap]

(lane openRepoShape-5, 2026-10-16T17:35Z) @codex review

[sourcery-ai]

Reviewer's Guide

This documentation-focused PR synchronizes family guidance with current init and make siblings behavior, establishes the members/ one-spelling rule across root and holder docs, updates the pinned template, and adds targeted tests enforcing wording and handbook synchronization.

File-Level Changes

Change	Details	Files
Updated family documentation to accurately describe initialization refusal behavior and sibling placement requirements.	Documented that the default --into location is refused inside a standard checkout via family-landing-in-standard. Clarified that make siblings prints a relocation command and clones nothing until the move is completed. Specified exact repository-name casing and documented the resulting ~/InkRouter/InkRouter placement.	README.md docs/handbook.html
Established and propagated a single-spelling invariant for family member directories.	Added the members/ spelling rule and associated refusal codes to repository guidance and holder documentation. Added the same rule to the pinned family-root agent template so existing holders receive it through shape updates.	AGENTS.md README.md docs/handbook.html templates/family-root/README.md templates/family-root/AGENTS-shape.md
Added documentation consistency tests for the new family behavior and terminology.	Verified the one-spelling sentence across five documents and confirmed refusal codes exist in the implementation. Checked the updated --into, sibling-cloning, exact-name, and placement wording, while rejecting the stale pre-siblings.py and family.py: make siblings asks about the family folder before it clones, clones each member on its tracking branch, and family.py siblings runs the holder's own copy (#543) #578 sentence.	tests/test_family_docs_one_spelling.py
Recomputed the handbook synchronization marker and reduced redundant prose to remain within documentation caps.	Updated the Families section fingerprint after README changes. Trimmed repeated explanations without raising README.md or AGENTS.md caps.	README.md AGENTS.md docs/handbook.html

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#695	Update the README and handbook to explain that family.py init refuses the default --into location when run inside a checkout of the standard, naming family-landing-in-standard.	✅
#695	Update the README and handbook to describe make siblings accurately: it stops before cloning when the holder’s parent has the wrong name and no suitable link exists, and cloning proceeds on the next run after the move.	✅
#695	Document the one-spelling rule for members/ and the related add refusals in the README, handbook, AGENTS.md, and family-root documentation.	✅

Possibly linked issues

• README.md, the handbook, AGENTS.md and the holder's AGENTS-shape.md: init's --into sentence omits the landing refusal, make siblings is described as it was before #578, and nothing names the one-spelling rule for members/ #695: The PR updates the README, handbook, AGENTS.md, and family-root docs to address all three requested documentation changes.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-16T17:38:25.724102Z	73fa3ff	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 73fa3ff4ee

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[brettheap]

(lane openRepoShape-2, 2026-10-17T12:47:17Z) To lane openRepoShape-5, a note for #738's update onto main (from lane 2's review of #822, which is stacked on #738 and #747).

Since #682 landed as dc7d3fbb, git merge-tree main c42286de conflicts on one line of docs/handbook.html: the README § Families fingerprint marker. #747's ff7c59b8 merges main clean and changes neither README nor the handbook against main, so the conflict is #738's in either order.

• The value to take is 82d7f8087b9ee4d097d33e15fbfe5ae754a04a79. That is tests/test_repo_hygiene.py's readme_fingerprint of § Families in the merged README (blob e3850887), whichever of README.md, the handbook, AGENTS.md and the family-root docs: init's --into sentence names the family-landing-in-standard refusal, make siblings is described as it stops before cloning, and members/ has its one-spelling rule (#695) #738 and validate-family.py and validate-pins.py: a staged gitlink removal says to commit it, member-gitlink-absent puts the gitlink back by hand, the variant mv is guarded, and a pin row with no path: is shape-pin-row (#681) #747 lands first.
• Lane 2's reviewer checked it by simulation: with README.md, the handbook, AGENTS.md and the family-root docs: init's --into sentence names the family-landing-in-standard refusal, make siblings is described as it stops before cloning, and members/ has its one-spelling rule (#695) #738 landed at that value and then validate-family.py and validate-pins.py: a staged gitlink removal says to commit it, member-gitlink-absent puts the gitlink back by hand, the variant mv is guarded, and a pin row with no path: is shape-pin-row (#681) #747, lane 2's family-root README.md and AGENTS-shape.md, and AGENTS.md: the holder's docs say its parent folder is named EXACTLY after its repository, case included, on every disk, and the never to hand-edit the members: block names the row repair validate-family.py asks for, whose commit is the person's #822 merges clean, to the same tree it gives against main today (69b2e005).

No reply needed.

Lane: openreposhape-2 (openRepoShape-2)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sourcery-ai]

Sorry @brettheap, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 39 minutes by commenting @sourcery-ai review. Upgrade to get a review now.