Local bug report issues/smart-model-routing-not-implemented.md has no corresponding Forgejo issue #8

New issue

Closed

opened 2026-05-09 00:19:52 +00:00 by Mark · 1 comment

Mark commented

2026-05-09 00:19:52 +00:00

Owner

Bug

Date: 2026-05-08
Severity: Low (tracking inconsistency)

Summary

A detailed bug report exists at issues/smart-model-routing-not-implemented.md in the repository documenting that smart_model_routing config is accepted but has zero implementation. However, there is no corresponding Forgejo issue tracking this bug.

Forgejo issue #2 is a feature request to implement smart model routing — it references the local bug report but does not serve as the bug tracker for the dead-config issue itself.

Impact

Anyone looking at the Forgejo issue tracker sees #2 (feature request) but not the underlying bug (config accepted but does nothing)
No way to close/resolve the bug independently of the feature request
Inconsistent tracking between repo-local docs and Forgejo

Suggested Fix

Either:

Delete the local .md file and let Forgejo be the single source of truth (this issue serves as that bug tracker)
Or keep the local file but add a header linking to this Forgejo issue
Or close this as a duplicate of #2 if the intent is to track implementation only

Tags

#infrastructure #tracking #consistency

## Bug **Date:** 2026-05-08 **Severity:** Low (tracking inconsistency) ## Summary A detailed bug report exists at `issues/smart-model-routing-not-implemented.md` in the repository documenting that `smart_model_routing` config is accepted but has zero implementation. However, there is no corresponding Forgejo issue tracking this bug. Forgejo issue #2 is a **feature request** to *implement* smart model routing — it references the local bug report but does not serve as the bug tracker for the dead-config issue itself. ## Impact - Anyone looking at the Forgejo issue tracker sees #2 (feature request) but not the underlying bug (config accepted but does nothing) - No way to close/resolve the bug independently of the feature request - Inconsistent tracking between repo-local docs and Forgejo ## Suggested Fix Either: 1. Delete the local `.md` file and let Forgejo be the single source of truth (this issue serves as that bug tracker) 2. Or keep the local file but add a header linking to this Forgejo issue 3. Or close this as a duplicate of #2 if the intent is to track implementation only ## Tags #infrastructure #tracking #consistency