Confirm hints

Confirm hints, by ID (hintIds) or all of one element (ref, target): writes the current target version into the relation or inline reference (in the text or in a property marked markdown, SR-127; relation.outdated) or into the replaces item (variant.core-changed, SR-045), and nothing else but the current titles of the file’s same-repository targets (D-042); an ID no open hint has gives a warning, for example one confirmed already.

Command hint.confirm. Writes files in the working tree, never to Git. It is refused while the workspace is read-only. Writes the current version of the target, which depends on the metamodel (which properties count).

Input

Field	Type	Required	Description
hintIds	array of string	no	IDs of hints to confirm (hintId of hint.list).
ref	elementRef	no	Confirm the open confirmable hints about this element: the outdated relations and inline references (in the text and in properties marked markdown) its file stores, and its replaces items onto a changed core requirement. A variant with open variant.core-changed-since-baseline or variant.core-new-since-baseline hints, without kind, gives hint.not-confirmable for them, since a new baseline of the variant settles them (SR-103 AK5).
target	elementRef	no	Confirm the open confirmable hints on relations and inline references that point at this element, for example after it changed.
kind	array of problemCode	no	Only selected hints with one of these codes (with ref or target); the confirmable codes are relation.outdated and variant.core-changed; variant.core-changed-since-baseline and variant.core-new-since-baseline give hint.not-confirmable, since a new baseline of the variant settles them (SR-103 AK5).

Output

Field	Type	Required	Description
confirmed	array of string	yes
files	array of string	yes
problems	array of problem	no

App

In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command Confirm hints. Key: Ctrl+K H (macOS ⌘K H).

CLI

reqseq hint confirm, with --json for the output as JSON. Its help:

Usage: reqseq hint confirm [options]

Confirm hints, by ID (hintIds) or all of one element (ref, target): writes the
current target version into the relation or inline reference (in the text or in
a property marked `markdown`, SR-127; `relation.outdated`) or into the
`replaces` item (`variant.core-changed`, SR-045), and nothing else but the
current titles of the file's same-repository targets (D-042); an ID no open hint
has gives a warning, for example one confirmed already.

Options:
  --hint-ids <value>      IDs of hints to confirm (`hintId` of hint.list).
                          repeatable
  --ref <value>           Confirm the open confirmable hints about this element:
                          the outdated relations and inline references (in the
                          text and in properties marked `markdown`) its file
                          stores, and its `replaces` items onto a changed core
                          requirement. A variant with open
                          `variant.core-changed-since-baseline` or
                          `variant.core-new-since-baseline` hints, without
                          `kind`, gives `hint.not-confirmable` for them, since a
                          new baseline of the variant settles them (SR-103 AK5).
  --target <value>        Confirm the open confirmable hints on relations and
                          inline references that point at this element, for
                          example after it changed.
  --kind <value>          Only selected hints with one of these codes (with
                          `ref` or `target`); the confirmable codes are
                          `relation.outdated` and `variant.core-changed`;
                          `variant.core-changed-since-baseline` and
                          `variant.core-new-since-baseline` give
                          `hint.not-confirmable`, since a new baseline of the
                          variant settles them (SR-103 AK5). repeatable
  --input <json|@file|->  command input as JSON: inline, from a file, or from
                          standard input
  --workspace <path>      workspace root (default: nearest folder upwards with
                          reqseq-workspace.yaml)
  --json                  print exactly the command output as JSON
  --yaml                  print the whole command output as YAML, problems one
                          per line
  -h, --help              show help

API

POST /v1/commands/hint.confirm on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.

MCP

Tool hint_confirm of the MCP server (reqseq mcp), with the input as its arguments.