chore: commit the repo config the project actually runs under #209

Merged

john merged 1 commit from chore/repo-config into main 2026-08-18 09:53:36 +00:00

Conversation 0 Commits 1 Files changed 1 +2 -61

john commented 2026-08-18 09:53:32 +00:00

Owner

Copy link

The committed repo layer still described the pre-cost-cut project: diff blocking, phase_diff and plan adjudicated, consult on, deepseek beside openai as a second reviewer, all eight risk surfaces, and three provider tier blocks.

None of that has been in force for a while. The whole v3.5.3 milestone ran under the stripped layer, and its own run record shows it: the diff trigger never fired, every review went to openai alone, and the phase-5 structural checkpoint offered no consult.

Leaving it uncommitted meant a fresh clone silently reverting to the expensive settings with nothing to say it had. The repo layer now carries only what this project actually pins - the three answered risk surfaces - and everything else resolves from the global layer or the stakes level.

The committed repo layer still described the pre-cost-cut project: `diff` blocking, `phase_diff` and `plan` adjudicated, consult on, deepseek beside openai as a second reviewer, all eight risk surfaces, and three provider tier blocks. None of that has been in force for a while. The whole v3.5.3 milestone ran under the stripped layer, and its own run record shows it: the `diff` trigger never fired, every review went to openai alone, and the phase-5 structural checkpoint offered no consult. Leaving it uncommitted meant a fresh clone silently reverting to the expensive settings with nothing to say it had. The repo layer now carries only what this project actually pins - the three answered risk surfaces - and everything else resolves from the global layer or the stakes level.

john added 1 commit 2026-08-18 09:53:32 +00:00

chore: commit the repo config the project actually runs under ... 26caff6e4a

The committed layer still described the pre-cost-cut project: diff blocking,
phase_diff and plan adjudicated, consult on, deepseek beside openai as a second
reviewer, all eight risk surfaces, and three provider tier blocks. None of that
has been in force for a while - the whole v3.5.3 milestone ran under the stripped
layer, which is visible in its own record: the diff trigger never fired, every
review went to openai alone, and the structural checkpoint offered no consult.

Leaving it uncommitted meant a fresh clone silently reverting to the expensive
settings with nothing to say it had. The repo layer now carries only what this
project actually pins - the three answered risk surfaces - and everything else
resolves from the global layer or the stakes level.

john merged commit 3f32c31326 into main 2026-08-18 09:53:36 +00:00

john referenced this pull request from a commit 2026-08-18 09:53:36 +00:00

Merge pull request 'chore: commit the repo config the project actually runs under' (#209) from chore/repo-config into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

already-shipped

Capability was already present in the shipped code when triaged; no work needed

  

bug

Something isn't working

  

documentation

Improvements or additions to documentation

  

duplicate

This issue or pull request already exists

  

enhancement

New feature or request

  

external-review

Raised by an outside code review; body carries the adjudication

  

good first issue

Good for newcomers

  

help wanted

Extra attention is needed

  

in progress

  

invalid

This doesn't seem right

  

needs-decision

Deliberate keep/cut call before any code

  

proposal

Make the case for a change before writing the code

  

question

Further information is requested

  

security

Hardening: a control that fails silently or an exposure surface

  

wontfix

This will not be worked on

No labels

already-shipped

bug

documentation

duplicate

enhancement

external-review

good first issue

help wanted

in progress

invalid

needs-decision

proposal

question

security

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: crenshawdev/cadence-archived#209

No description provided.