Skip to content

AGENTS.md follow-up - #3912

Open
mcfnord wants to merge 3 commits into
jamulussoftware:mainfrom
mcfnord:agents-3785-followup
Open

AGENTS.md follow-up#3912
mcfnord wants to merge 3 commits into
jamulussoftware:mainfrom
mcfnord:agents-3785-followup

Conversation

@mcfnord

@mcfnord mcfnord commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

🤖 AI: Follow-up to #3785, on the invitation there. Three one-line changes; each traces to a point raised in that review, each stands alone, and any can be dropped if it fails the stable-and-general bar.

Nothing here adds a rule to AGENTS.md: 3 insertions against 3 deletions, so the file gains no line and ends at 654 words against 651 on main. On #3910 the point was made that CONTRIBUTING.md is the primary source of truth, with AGENTS.md as the guidance to it — so a rule stated only in the agent file is the defect, not the fix. Three candidates that would otherwise have landed here are held for CONTRIBUTING.md: wire-format compatibility, the clang-format lists that have to move together, and treating a code comment or a commit message as a claim like any other.

Short description of changes

AGENTS.md:

  • Testing names the build it needs. The Build line's CONFIG+=headless serveronly binary rejects the Testing line's client — built from 11a28d57 and run: ./Jamulus -n -c localhostClient only option(s) '--connect' used. See '--help' for help, exit 1. One clause closes the contradiction (raised in review, pljones preferring the plain build).
  • Duplicates cut, per the 2026-07-28 brevity pass: "One logical change per PR" and "Builds? Tested? Smallest change possible?" repeat line 5 and the Testing and Always lines, in a file prepended to every prompt.

docs/agents/COMMENTING.md: the last bullet was the fragment "Disclose AI-generated text" and now names where the form is stated, rather than carrying a second copy of it.

CHANGELOG: SKIP

Context: Fixes an issue?

Follow-up to #3785.

Does this change need documentation? What needs to be documented and how?

No — it is documentation.

Status of this Pull Request

Ready for review. One commit per change, so any line is droppable in isolation.

What is missing until this pull request can be merged?

Maintainer judgment on which lines clear the "stable and general" bar.

Checklist

  • I've verified that this Pull Request follows the general code principles
  • I tested my code and it does what I want — the one testable claim (a serveronly binary rejects -c) was built and run; output above. No code is changed.
  • My code follows the style guide — Markdown only.
  • I waited some time after this Pull Request was opened and all GitHub checks completed without errors.
  • I've filled all the content above

🤖 This message was written by AI and reviewed by @mcfnord.

@mcfnord mcfnord changed the title AGENTS.md follow-up: apply the #3785 review points that did not land AGENTS.md follow-up Aug 18, 2026
jrd and others added 3 commits August 18, 2026 23:40
The Build line offers a CONFIG+=headless serveronly build; the Testing line
then connects a client. That binary rejects -c:

    $ ./Jamulus -n -c localhost
    ./Jamulus: Client only option(s) '--connect' used.  See '--help' for help
    (exit 1; built from 11a28d5)

One clause closes the contradiction.

CHANGELOG: SKIP

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
'One logical change per PR' and 'smallest change' are line 5, bold, above the
fold; 'Builds? Tested?' are the Testing and Always lines. This file is
prepended to every prompt, so each repeat costs context on every call.
'See CONTRIBUTING.md' stays in Read when relevant, where it carries a
when-to-read note.

CHANGELOG: SKIP

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The last bullet was the fragment "Disclose AI-generated text" with no form and no
pointer. It now names where the rule is stated rather than restating it, so there is
still one copy of the form and it is the one in AGENTS.md.
@mcfnord
mcfnord force-pushed the agents-3785-followup branch from 71143f6 to f63cbe7 Compare August 18, 2026 23:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant