Skip to content

chore: declare labels.lane_other and curate_route_threshold in .oss.json (#411) - #418

Merged
fdaviddpt merged 1 commit into
mainfrom
fix/411
Sep 18, 2026
Merged

fdaviddpt merged 1 commit into
mainfrom
fix/411

Conversation

@fdaviddpt

Copy link
Copy Markdown
Contributor

Two keys oss:doctor measured on 2026-09-17, split out of its larger scaffold refresh so they can land on their own.

oss_config.py --validate passes. No code change.

Closes #411

🤖 Generated with Claude Code

[AI-generated]

…son (#411)

The tracker already carried a lane-other label with nothing in .oss.json
declaring it, which the triage step reported as #411. And with no
curate_route_threshold set, next_action.py could never check trap.d/ and
kept reporting curate as not-configured rather than due or not-due.

Both values are the ones oss:doctor measured on 2026-09-17; the threshold
of 15 is the same decision the oss plugin's own repository made. Split
out of that doctor run's larger scaffold refresh, which is a separate
review.

Closes #411

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@fdaviddpt fdaviddpt added the no-changelog Change is invisible to users label Sep 18, 2026
@fdaviddpt
fdaviddpt merged commit a729811 into main Sep 18, 2026
13 of 15 checks passed
@fdaviddpt
fdaviddpt deleted the fix/411 branch September 18, 2026 05:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog Change is invisible to users

Projects

None yet

Development

Successfully merging this pull request may close these issues.

triage: lane-other label exists on the tracker but .oss.json never declares labels.lane_other

1 participant