Crc Run controllers build RunPath in the initializer; find the missing run config #1117
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#1117
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The
Crc::*::Runcontrollers buildCrc::RunPathin their initializers. A controller that builds its own dependency hides that dependency from its caller and from its tests. A lint cop and a lesson exist for a dependency built in an initializer. The cop did not flag these files. Jared suspects that an object is missing betweenCrc::*::RunandCrc::RunPath: a run config that holds the attributes of one run and goes to the controller whole, for exampleRun.new(config: run_config).Crc::RunPathitself may be that config.Observed
Crc::Census::SettingsandCrc::Sweep::Settingsalso buildRunPath.within(project, run[:run_dir]).A related question:
Crc::RunPathandCollaboratorPass::RunDirectorymay be one domain concept with two names. The proposed glossary term is "Run: the saved output of one pass over a target".Reproduce
n/a: design ticket. The first step is to find the cop and the lesson and to find why the cop did not flag
crc/jobs/run.rb.Origin
data_clump project+runin rundocs/crc/os-sdlc/collaborator-runs/20261018T172139Z.Occurrence: crc command controllers take a typed request Settings object, not the parsed Hash
Seen: plugins/os-sdlc/lib/os_sdlc/crc//run.rb (11 sites of RunPath.within(project, x.fetch(:run_dir)); 7 controllers and 2 Settings.for builders still take the Hash as
run)Run: session 86f833b9 (run 3 retrospective, 2026-10-20)
Adds: #1194 renamed 5 of 14 Hash takers and the name_collision count fell 50 to 14 while 9 homonyms stayed untyped. The answer to this ticket's open question: one Settings value object per command in the Census::Settings / Sweep::Settings shape, with .for(project, request) building run_path once; add the glossary entry for the parsed command request in plugins/os-sdlc/CONTEXT.md before naming the class (do not default to
request). The Crc::::Run class names carry the same clash with glossary Run.