• Add requirement tracing markers to implementations
• Consolidate duplicate requirement definitions in documentation
• Update requirement documentation with implementation status
• Add missing YAML frontmatter to requirements file

Link OpenUrlAction to UX requirement

• Add requirement tracing comment linking implementation to req~ux.disabled-vs-hidden~1
• Comment marks the exact example from the requirement specification

jabgui/src/main/java/org/jabref/gui/maintable/OpenUrlAction.java

Link JabKit banner to CLI requirement

• Add requirement tracing comment linking CLI banner implementation to
 req~jabkit.cli.banner-shown~1
• Comment documents the implementation of the banner display requirement

jabkit/src/main/java/org/jabref/toolkit/JabKitLauncher.java

Remove duplicate requirement reference

• Remove duplicate requirement definition req~ui.dialogs.confirmation.naming~1
• Replace with link to canonical definition in ux.md
• Remove "Needs: impl" status from duplicate reference

docs/code-howtos/ui-recommendations.md

Description

The newly added OpenFastTrace link // [impl->req~jabkit.cli.banner-shown~1] marks the CLI banner
requirement as implemented, but JabKit.run() still prints the banner in non-help scenarios (e.g.,
running the root command with only global flags like -p). This makes requirement tracing
misleading because the documented requirement says the banner is only shown when help is output.

Code

jabkit/src/main/java/org/jabref/toolkit/JabKitLauncher.java[R80-82]

+            // [impl->req~jabkit.cli.banner-shown~1]
            String usageHeader = BuildInfo.JABREF_BANNER.formatted(buildInfo.version) + "\n" + JABKIT_BRAND;
            commandLine.getCommandSpec().usageMessage().header(usageHeader);

Evidence

The requirement explicitly limits banner output to help/no-command cases, but the root command’s
run() prints the banner whenever it executes (unless --version). Because SharedOptions
provides global flags like -p/--porcelain and -d/--debug, the root command can execute without
--help, contradicting the requirement while the PR now claims an implementation link at the
launcher’s usage-header setup.

docs/requirements/cli.md[16-24]
jabkit/src/main/java/org/jabref/toolkit/JabKitLauncher.java[78-92]
jabkit/src/main/java/org/jabref/toolkit/commands/JabKit.java[79-86]
jabkit/src/main/java/org/jabref/toolkit/commands/JabKit.java[251-260]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The PR adds an OpenFastTrace implementation link for `req~jabkit.cli.banner-shown~1`, but the current code path still prints the JabRef banner when the root `jabkit` command runs without help (e.g., `jabkit -p`). This makes the trace misleading and contradicts the requirement text.

### Issue Context
- Requirement: banner should be shown only when help is output / no command given.
- Current behavior: `JabKit.run()` prints the banner on root command execution (unless `--version`). With global flags (`-p`, `-d`) the root command can execute without `--help`.

### Fix Focus Areas
- jabkit/src/main/java/org/jabref/toolkit/JabKitLauncher.java[78-92]
- jabkit/src/main/java/org/jabref/toolkit/commands/JabKit.java[79-86]
- jabkit/src/main/java/org/jabref/toolkit/commands/JabKit.java[251-260]
- docs/requirements/cli.md[16-24]

### What to change
Implement one consistent approach:
1) **Preferred (align behavior to requirement):** ensure the root command does not execute `JabKit.run()` in non-help scenarios (e.g., require a subcommand or explicitly route “no subcommand / only global flags” to usage/help), and remove/adjust the unconditional banner printing in `JabKit.run()`.
2) If the current behavior is intended, **update the requirement text** to match reality and relocate/keep the `[impl->...]` link accordingly.

Finally, keep the `[impl->req~jabkit.cli.banner-shown~1]` marker only on code that truly enforces the requirement’s stated behavior.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools