You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature] Forge observation and doctor extensions (PR-3) #164
ainative doctor/status report installation state but have no concept of the
observed forge, remote candidates, Work Authority resolution state, or the
effective release source. Multi-Forge requires a read-only observation surface
that never dials out, never reads credentials, and never guesses a provider from
a hostname.
Source: Multi-Forge v1.3.2-final §55–59 (PR-3).
Expected outcome
ainative forge detect and ainative forge status describe what can be observed
locally about the project's remotes and features; doctor displays the effective
profile, feature set, Work Authority resolution state and release source — with
zero network, credentials, writes or persistent trust.
Acceptance criteria
Blocked until PR-1 green.
Commands ainative forge detect and ainative forge status exist and
satisfy: network calls = 0, credentials = 0, writes = 0, persistent
trust = 0.
Provider hints: github.com → github, gitlab.com → gitlab,
unknown/custom host → unknown; self-hosted provider detection is never
guessed from hostname alone.
Fork rendering: origin/upstream candidates are displayed without automatic
preference; ambiguity is rendered (e.g. Resolution: AMBIGUOUS).
Doctor extensions display: profile, assurance level, effective feature set,
observed remote candidates, Work Authority resolution state, release source,
release selection reason, release auth origin, unresolved ClaimAttempts —
never credentials.
Output is stable, machine-readable where the rest of the CLI is
(--json), and derived through the shared feature projection.
Multi-Forge implementation merged into dev (squash f0101fc via PR #172), full CI matrix green (52/52: Linux/Windows/macOS, py3.11/3.13). The Issue stays open until the final dev -> main promotion, per the maintainer rule that main is untouched until everything is tested and integrated.
The follow-up increment (mandatory secret-pattern floor, scenarios J/M/P, documentation parity) is merged into dev (squash a8e1fb6 via PR #174, CI 76/76 green). The Issue stays open until the final dev -> main promotion.
Activity
Rwanbt commentedon Sep 16, 2026
Claiming this Issue; implementation on \multiforge\ (local, CI at the end).
feat(forge): forge detection, status observation and the doctor exten…
feat: Multi-Forge implementation (features, claims, Release V3, GitLa…
Rwanbt commentedon Sep 16, 2026
Multi-Forge implementation merged into
dev(squash f0101fc via PR #172), full CI matrix green (52/52: Linux/Windows/macOS, py3.11/3.13). The Issue stays open until the finaldev->mainpromotion, per the maintainer rule thatmainis untouched until everything is tested and integrated.Rwanbt commentedon Sep 16, 2026
The follow-up increment (mandatory secret-pattern floor, scenarios J/M/P, documentation parity) is merged into
dev(squash a8e1fb6 via PR #174, CI 76/76 green). The Issue stays open until the finaldev->mainpromotion.feat: Multi-Forge v1 — production promotion (dev -> main) (#176)
Rwanbt commentedon Sep 17, 2026
Done: the work is merged into
main(squash 8f319ad via PR #176, full CI matrix green including the Production Gate). Closed as completed.