I3397 — install-check's first-intent stage reaches a satisfied verdict in a named repository with only the getting-started commands, and counts the doctrine its output exposes

✕BLOCKED wave 4 · p1 · implementation profile · parallel safe

Part of a-newcomer-reaches-a-first-verified-intent — A newcomer reaches an intent whose verdict is satisfied, in a repository of their own, using only what the getting-started page shows.

Objective

Add a first-intent stage to scripts/ci/install-check after the --repository adoption: propose an intent, add a verify: criterion naming the repository's verify command, record the verification, and read intent explain until the verdict is satisfied. Record each step's seconds, the commands typed beyond those the built getting-started page shows, and the output lines matching declared doctrine patterns (an ADR number, a rule id, a path under .ai/repo the user did not create). Write it into the T1 or T6 trial record as the protocol declares and extend case 1024.

Why

T6 of the owner's report of 2026-10-19 asks that a newcomer not need internal doctrine; the scripted stage measures the path's tool cost per platform and makes 'without doctrine' a count of declared patterns rather than an impression.

Current state

scripts/ci/install-check:17-27 has no intent stage; test/cases/1024_an_installed_release_serves_a_foreign_repository.sh exercises a local fixture.

Desired state

Case 1024 reaches a satisfied verdict with zero commands beyond the page and records the doctrine-line count.

Scope

• scripts/ci/install-check
• test/cases/1024_an_installed_release_serves_a_foreign_repository.sh

Out of scope

• A live agent session in CI
• Rewording command output (each doctrine line becomes its own issue)

Dependencies

• I3396✕BLOCKED A documented command adds a criterion to a proposed intent, and the getting-started page shows the path from a proposal to a satisfied verdict
• I3361✕BLOCKED install-check's first-run stage runs against a clone of an existing repository named on the command line and writes a T1 trial record

Acceptance criteria

• The stage reaches verdict satisfied and records each step's seconds
• The count of commands beyond the page is zero
• The doctrine-line count is recorded with each matching line's pattern
• Without --repository the stage runs on case 1024's fixture

Validation

• bash test/run.sh 1024_an_installed_release_serves_a_foreign_repository
• majordomus plan validate

Evidence required

• case_first_intent_stage

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3397.yaml. Read it back with majordomus plan show I3397.