chore(build): fix clean/clean-all inconsistency and remove redundant build step

[github-actions]

🤖 This is an automated pull request from Repo Assist, an AI assistant for this repository.

Summary

Fixes two issues in the justfile build system:

1. clean / clean-all inconsistency

The clean recipe's own comment said it "preserves dotnet obj/bin directories", but the recipe body was deleting src/obj, src/bin, test/obj, and test/bin. This meant:

• clean and clean-all produced exactly the same result — clean-all was a no-op wrapper
• Every just build (which calls clean) performed a full dotnet restore from scratch, discarding the NuGet package cache

After this fix:

• clean removes only Fable/Python build outputs and example artifacts. The .NET obj/bin directories are preserved so incremental dotnet build is fast.
• clean-all (via clean + explicit removals) fully wipes obj/bin and forces a fresh NuGet restore. Use this when you want a guaranteed clean slate.

2. Redundant dotnet build in test recipe

# before
test: build
    dotnet build \{\{test_path}}   ← redundant
    dotnet run --project \{\{test_path}}

dotnet run always performs an implicit build before executing. The explicit dotnet build \{\{test_path}} step ran the same compilation twice, adding build time with no benefit. Removed.

Impact

• Developer experience: just build and just test are faster because .NET restore/compilation is incremental instead of always starting from scratch.
• No behaviour change for CI: CI always runs on a fresh runner, so clean vs clean-all semantics make no difference in CI. The build output is identical.
• just clean-all is now meaningfully different from just clean — use it when you need a true fresh start.

Files changed

• justfile — four lines removed, one comment updated

Note

🔒 Integrity filter blocked 10 items

The following items were blocked because they don't meet the GitHub integrity level.

• support for asynchronous context managers #134 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• allow TextIOWrapper to be enumerated #131 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• auto pip installation of dependencies during compilation of scripts #117 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• typeshed: generate bindings automatically ~ python glutinum? #115 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Pandas binding #65 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Support for Attributes? #48 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• string format specifier '{i:X4}' not working #36 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Create Pyi parser #22 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• Roadmap #15 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• How does it generate the python source from AST? #5 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Repo Assist · ● 2M · ◷