Repository navigation
v2026.11.11
What's Changed
- [Core] A
manual:check that names the Reviewer or Security runs in its step-8 round, not as a step-7 test, andplan-check.pyrefuses one that names a member outside the tier's review round; a Product Manager's manual check named only in the plan's prose holds the review, and an Orchestrator7 Manual testrow records a stand-in's (#396) - [Core] A member's report re-sent word for word after a task notification is part of its round, not a continued launch; members send their report once, with no background command left running (#397)
- [Core]
squad-log.pynames--round 1when a round is logged late;squad-next.pyasks for the verbatim row before stamping a documentation-only fix of an open review round that no Dev or Tester fix followed (#398) - [Core]
plan-check.pyskips appended challenge and security notes in its placeholder check; notes the Lead answered in Challenge are not asked for again (the template's own Challenge text answers none) (#401) - [Core] Security's diff verdict counts its non-blocking findings (
VERDICT: APPROVED | NON-BLOCKING n, else its tags), so tiersdocsandpatchdecide them before the PR; thepatchtest is written on the unfixed head before the edits (#402) - [Core]
squad-notes.pywrites a report's control characters as text escapes, so appended notes never failplan-check.py(#400) - [Core] The Dev's skeleton report lists the changed files from
git statusand only members read back from disk, andsquad-next.pysends a file a skeleton task row names but the branch has not changed back to the Dev before tests first; a plan names the test seam of a resource bound over an external system (#399) - [Core]
lesson-label.pycounts only the tools the template ships to.squad/tools/as managed, so a repository's own tool there is labelledsquad; Template-managed files names the template blocks of.editorconfigas marked (#395) - [Core]
result.mdis listed in the work folder (specs/README.md, Work folder) and posted in the working record of tiersdocsandpatch(#394) - [Profile] The seeded CI of every profile runs
decision-check.py --require-history --tags-fetchedin a jobdecision-records, so a changed released record cannot merge, and a refresh adds the job to an existing CI; a CI merged from several profiles runs it once and renames a prefixed job inneeds:too (#403) - [Profile] dotnet: the shared global analyzer config sets MSTEST0001, a rule reported without a location that no
.editorconfigsection reaches, toerror;dotnet-rules.pywrites a pending entry for such a rule into.squad/dotnet-rules-pending.globalconfigat a higherglobal_level, anddotnet_config.pychecks thatDirectory.Build.props, Dockerfiles and.dockerignorecarry both global configs (#393) - [Profile] dotnet:
.squad/dotnet-rules-pending.globalconfigkeeps the line ending of its checkout, so a CRLF repository's fresh clone passes the Analyzer gate;scope-check.pylets a product PR change it withsquad_settings.py, from which it is generated (#406) - [Core]
plan-check.pyrefuses amanual:check that names a member who reviews no diff (Lead, Dev, Tester, …), so it is no longer taken for the Product Manager's test; Work folder names the feature'sdocsroute (#408) - [Seed] The seeded CI workflows gain the
decision-recordsjob; dotnetDirectory.Build.propsnames.squad/dotnet-rules-pending.globalconfig, and dotnetstack.mdsays the Analyzer gate also reports a diagnostic without a location of a project with a changed file (#393, #403) - [Seed] Seeded files changed; existing targets keep their own copy, so the refresh carries these changes over by hand:
profiles/dotnet/seed/.github/workflows/ci.yml,profiles/dotnet/seed/.squad/stack.md,profiles/dotnet/seed/Directory.Build.props,profiles/go/seed/.github/workflows/ci.yml,profiles/node/seed/.github/workflows/ci.yml,profiles/typescript/seed/.github/workflows/ci.yml
Full Changelog: v2026.11.10...v2026.11.11