A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I1996

doctor does not fail an adopter on a check written for this repository

Where it stands

devtask.issue

Readiness: complete completion is recorded and every required evidence token is present
Status: DONE
Can start: not now
Milestone: adopter-upgrades
Milestone status: ACTIVE
Wave: 0
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 2 of 2

Moves

plan.transition

What it is

Objective: Stop `majordomus doctor` from failing an adopter's repository on the reasoning design's own coupling rules, and stop its reproduce hints from naming paths only this repository has.
Why: lib/doctor.sh runs the executable's `reasoning check` against whatever repository it is in. Run by majordomus 0.14.0 in prismatic-platform on 2026-10-08, doctor exited 10 on three findings about the adopter's own files: '.github/workflows/archive/ci.yml — ci: CI names the model credential ANTHROPIC_API_KEY; no gate may depend on a live model', the same for OPENAI_API_KEY, and 'docs/adrs/adr-0023-ollama-model-integration-architecture.md — claims: asserts requires ollama, a claim the reasoning design refuses'. The workflow is an archived, inactive GitHub workflow in a GitLab-hosted repository, and the ADR is the adopter's own architecture decision. Each line ends '[reproduce: bin/majordomus-cli reasoning check]', a path that exists only here. A scratch copy holding only .ai/, the bootstraps and .githooks reported no finding, so the check is judging the adopter's product, not its use of the reasoning layer. The same adopter then ran this repository's own bin/majordomus (0.17.0, 4090b2b8ae) against the same layer and the three lines did not appear, although apps/majordomus-cli/src/reasoning is unchanged since v0.14.0: whether the check stopped reaching the adopter's files or stopped running at all there is not established, and establishing it is the first step.
Now: The ci and claims families of `reasoning check` scan every workflow and document of the repository they run in and fail doctor on a match. Reproduce hints name bin/majordomus-cli.
Wanted: In a repository that is not this one, the reasoning check holds only what the adopter adopted: its own catalogue, adapters and records. A rule about what Majordomus's CI and Majordomus's claims may say is not applied to an adopter's workflows and documents, or is advisory there. Every reproduce hint names a command the adopter can run.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Acceptance

doctor in a fixture adopter repository whose workflow names a model credential and whose document says 'requires ollama' reports no reasoning failure
The same two files in this repository are still refused
No reproduce hint doctor prints in an adopter repository names bin/majordomus-cli

Validation: bin/majordomus plan validateMJ_TEST_JOBS=4 bash test/run.sh <the case this issue adds>
Evidence required: adopter_reasoning_check_casereproduce_hint_is_runnable_case
Evidence present: adopter_reasoning_check_casereproduce_hint_is_runnable_case

Scope

Touches: lib/doctor.shapps/majordomus-cli/src/reasoningapps/majordomus-cli/src/capability/builtin/reasoning.rsdocs/REASONING.mdtest/cases
Not: unknown: the record declares no `non_scope`
Depends on: unknown: the record declares no `depends_on`
Priority: p2
Profile: implementation
Parallel safe: true
Owner: unknown: the record declares no `owner`

The work so far

Branches: none
Merged: none
Commits: 0
Trunk: master
Sessions: none
Created: 2026-10-08
Updated: 2026-10-14T13:31:45Z
Started: 2026-10-14T13:31:26Z
Verified: unknown: the record declares no `verified_at`
Completed: 2026-10-14T13:31:45Z

Synchronisation

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.