A word-character citation marker such as _ makes unqualified citations invisible, because citation_re requires a word boundary before the ID

[vjovanov]

What happens

A project that sets [reference] marker = "_" and [id] format = "{kind}_{slug}":

# grund.toml
grund_config_version = 1

[id]
format = "{kind}_{slug}"

[reference]
marker = "_"

[fmt.cross_refs]
enabled = false

# docs/functional-spec/FS-login.md
# FS_login: Login

Lead.

// src/lib.rs
//! _FS_login

grund FS_login resolves the declaration and prints Lead., but the citation in src/lib.rs is not seen anywhere. grund refs FS_login exits 0 and prints nothing, grund cover gives src/lib.rs no citations, and grund check warns declared but never cited: FS_login. The same fixture with the default marker § (//! §FS_login) works.

A reproducer builds grund and runs both fixtures side by side. On grund 0.16.2-dev at af9f6f5 it printed:

grund: grund 0.16.2-dev at af9f6f56d26721898b13c9a853a9044059a387ab
control, marker '§', src/lib.rs = '//! §FS_login':
  grund refs FS_login:
    src/lib.rs:1: §FS_login
  grund cover --format json:
    {"path":"docs/functional-spec/FS-login.md","citations":[]}
    {"path":"src/lib.rs","citations":[{"path":"src/lib.rs","line":1,"column":5,"id":"FS_login","section":null,"marker":true,"text":"§FS_login","enclosing_declaration":null,"enclosing_section":null}]}
subject, marker '_', src/lib.rs = '//! _FS_login':
  grund refs FS_login:
    
  grund cover --format json:
    {"path":"docs/functional-spec/FS-login.md","citations":[]}
    {"path":"src/lib.rs","citations":[]}
expected: refs=1 cover=1 (the configured marker cites the declared FS_login, as '§' does)
observed: refs=0 cover=0
defect stands: underscore-marked unqualified citation is invisible (citation_re's \b before the ID)

The same happens with the installed 0.15.1-dev, so it is not new. The LSP is affected as well: a textDocument/definition request inside //! 😀 _FS_login returns result: null, while § resolves. The reproducer above covers only the CLI.

The cause looks like crates/grund-core/src/grammar/compiled.rs:372:

let citation_re = Regex::new(&format!(r"\b{}{}{}", namespace_prefix, id_pat, sec_suffix))?;

The \b in front of the ID needs a word boundary before the F. When the marker is itself a word character, as _ is, the marker and the ID sit inside one word and there is no boundary, so the unqualified citation never matches. The marker fallback in the scanner handles qualified citations (_alias/FS_login), so only the unqualified spelling, which is the common one, is lost.

What should happen

_FS_login should be read as a marked citation of FS_login, exactly as §FS_login is under the default marker. It should show up in refs and cover, satisfy check, and resolve through LSP definition. A citation is the configured marker followed by an ID (§FS-check.1.1), and the marker can be configured (§FS-config.3.1). Config loading accepts _ without a complaint. The word boundary is there to keep an ID from matching inside a longer word, and the marker that ends right before the ID already does that job.

If a word-character marker is not meant to be supported, then grund.toml should reject it at load time, not accept it and then see nothing.

Why it matters

The failure is silent. refs comes back empty and cover lists the file with no citations. check raises no dangling-citation error, only a misleading declared but never cited warning on the declaration that is in fact cited. fmt reports nothing to normalize. A project on this marker loses every edge from code to spec, and nothing tells it so. Any rule that relies on those edges (grounding, chapter rules, refs before a rename) runs against a graph that is missing them.

What else was tried

• The control with marker § in the same fixture finds the citation, so the fixture and the ID format are fine.
• grund FS_login resolves the declaration, so declaration parsing under {kind}_{slug} works. Only citation scanning fails.
• The LSP definition request fails the same way with or without a trailing newline and with or without prose after the citation.
• This came up while reviewing Complete LSP citation authoring with ID completion and reliable trigger interaction #472. That issue's overlap tests were written so they don't depend on it, and the scanner fix was explicitly left out of its scope.

Workaround

Use a marker that is not a word character (the default §, for example). None found that keeps _.

Filed by grounded-ticket intake from grund.57 (kind: bug).

[vjovanov]

Record · 31 transitions · now completed · last 2026-10-06 06:11Z
Holder vjovanov@kung-fu-workstation · since 2026-10-06 05:02Z

1 · supervising → supervising 2026-10-06 05:04Z · `PATH: simple`

plan runtime/supervision/plan.md

Supervision plan for #483

Ticket

Reference: #483
Title: A word-character citation marker such as _ makes unqualified citations invisible, because citation_re requires a word boundary before the ID
State when fetched: OPEN

Ticket body, verbatim:

What happens

A project that sets [reference] marker = "_" and [id] format = "{kind}_{slug}":

# grund.toml
grund_config_version = 1

[id]
format = "{kind}_{slug}"

[reference]
marker = "_"

[fmt.cross_refs]
enabled = false

# docs/functional-spec/FS-login.md
# FS_login: Login

Lead.

// src/lib.rs
//! _FS_login

grund FS_login resolves the declaration and prints Lead., but the citation in src/lib.rs is not seen anywhere. grund refs FS_login exits 0 and prints nothing, grund cover gives src/lib.rs no citations, and grund check warns declared but never cited: FS_login. The same fixture with the default marker § (//! §FS_login) works.

A reproducer builds grund and runs both fixtures side by side. On grund 0.16.2-dev at af9f6f5 it printed:

grund: grund 0.16.2-dev at af9f6f56d26721898b13c9a853a9044059a387ab
control, marker '§', src/lib.rs = '//! §FS_login':
  grund refs FS_login:
    src/lib.rs:1: §FS_login
  grund cover --format json:
    {"path":"docs/functional-spec/FS-login.md","citations":[]}
    {"path":"src/lib.rs","citations":[{"path":"src/lib.rs","line":1,"column":5,"id":"FS_login","section":null,"marker":true,"text":"§FS_login","enclosing_declaration":null,"enclosing_section":null}]}
subject, marker '_', src/lib.rs = '//! _FS_login':
  grund refs FS_login:
    
  grund cover --format json:
    {"path":"docs/functional-spec/FS-login.md","citations":[]}
    {"path":"src/lib.rs","citations":[]}
expected: refs=1 cover=1 (the configured marker cites the declared FS_login, as '§' does)
observed: refs=0 cover=0
defect stands: underscore-marked unqualified citation is invisible (citation_re's \b before the ID)

The same happens with the installed 0.15.1-dev, so it is not new. The LSP is affected as well: a textDocument/definition request inside //! 😀 _FS_login returns result: null, while § resolves. The reproducer above covers only the CLI.

The cause looks like crates/grund-core/src/grammar/compiled.rs:372:

let citation_re = Regex::new(&format!(r"\b{}{}{}", namespace_prefix, id_pat, sec_suffix))?;

The \b in front of the ID needs a word boundary before the F. When the marker is itself a word character, as _ is, the marker and the ID sit inside one word and there is no boundary, so the unqualified citation never matches. The marker fallback in the scanner handles qualified citations (_alias/FS_login), so only the unqualified spelling, which is the common one, is lost.

What should happen

… cut at 3000 characters; the whole file is runtime/supervision/plan.md

decision runtime/supervision/decision.md

PATH: simple
PLANNER: -
REASON: No path label binds this issue. This is a reproduced bug with a named cause: the leading ID word boundary prevents the accepted underscore marker from yielding unqualified citations. The recorded upstream reproducer exits 1 at af9f6f5, which is also this checkout's HEAD. Recognizing the configured marker restores the existing promise in FS-check.1.1 and FS-config.3.1; it changes no configuration, default, public signature, or intended citation policy. Of the ticket's remedies, support the already accepted marker rather than introduce a configuration rejection. Triage took the existing-validation shortcut and supplied no fresh reproduction or SIZE line; specify must supply current failing evidence and separately pin the reported LSP symptom before implementation.

2 · ticket.triage · intake → validated 2026-10-06 05:04Z

ticket runtime/ticket/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage.json

{
"task_id": "github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage",
"origin": "issue",
"repo": "agent-grounds/grund",
"number": 483,
"url": "#483",
"kind": "bug",
"tool": "grund",
"title": "A word-character citation marker such as _ makes unqualified citations invisible, because citation_re requires a word boundary before the ID",
"issue_state": "open",
"state_label": "state:deciding",
"path_label": "",
"checkout": "/home/vjovanov/ag/grund/fix/issue-483",
"labels": [
"bug",
"high-priority",
"state:deciding"
],
… cut at 3000 characters; the whole file is runtime/ticket/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage.json

3 · ticket.triage · validated → completed 2026-10-06 05:04Z

validation runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/validation.md

Validation of github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage: A word-character citation marker such as _ makes unqualified citations invisible, because citation_re requires a word boundary before the ID

• Kind: bug
• Origin: issue agent-grounds/grund#483 (A word-character citation marker such as _ makes unqualified citations invisible, because citation_re requires a word boundary before the ID #483)
• Verdict: none recorded
• Size: not stated

Artifacts

• runtime/ticket/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage.json

4 · ticket.clarify · clarifying → cancelled

5 · ticket.plan · planning → cancelled

6 · ticket.dependencies · dependencies → cancelled

7 · ticket.agora · agora → cancelled

8 · supervising → supervising 2026-10-06 05:04Z

9 · ticket.specify · specify → opening 2026-10-06 05:20Z · `PR: https://github.com//pull/484`

contract runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.specify/contract.md

Specification contract for issue #483

The fix must recognize an accepted word-character marker followed by an unqualified full ID as one marked citation in the shared CLI/LSP graph. No behavior implementation is included in this step. The opening program will push the specification commit and create the draft PR for #483; this step neither pushes nor opens a PR.

Specification commit: 92e078b015, Specify word-character citation marker recognition and regressions, on the unchanged branch fix/issue-483.

Ground written

• Added §FS-check.1.1.10 docs/functional-spec/FS-check.md:119. The explicit configured marker establishes the start without an intervening word boundary; the record keeps its marker position and authored token. Existing bare boundaries, sections, qualification, strict modes, full-ID precedence, and exclusions remain in force. Graph consumers see one edge; missing targets reach ordinary checking.
• Extended §FS-config.3.1 docs/functional-spec/FS-config.md:185 to explicitly support word characters in accepted markers.
• Extended §AR-scanner.2.3 docs/architecture/AR-scanner.md:168 to require shared recognition, one positioned record, and retained bare-token boundaries.
• Extended §FS-lsp.1.3 docs/functional-spec/FS-lsp.md:121 and §FS-lsp.4 docs/functional-spec/FS-lsp.md:383 for shared word-character recognition and UTF-16 definition navigation after a non-ASCII prefix.
• Added §DF-word-character-citation-markers docs/decisions/functional/DF-word-character-citation-markers.md:1, including .1 at line 6, .2 at line 17, and .release-note at line 46. Added its functional-decision index entry. No changelog entry.

The implementer must cite the new most-specific recognition point, FS-check.1.1.10, beside the shared repair. Do not implement configuration rejection, change bare-token boundaries globally, or add an editor-only fallback. Colon-format lookup and unrelated completion changes remain outside scope.

Tests and the single focused command

Run from /home/vjovanov/ag/grund/fix/issue-483:

cargo test --workspace --locked --no-fail-fast --target-dir "$HOME/ag/tmp/grund-issue-483-target" word_character_marker -- --nocapture

Observed exit: 101. Exact full output is in runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/tests.log under this workspace. There are four failing tests and one passing preservation guard across three targets. The failure is from assertions after successful compilation and protocol initialization, not the environment.

CLI end-to-end test

File: crates/grund-cli/tests/e2e.rs; test: word_character_marker_cli_contract.

It runs eight new immutable golden cases under tests/e2e/cases/, also discovered by the ordinary e2e_cases_match_expected_reports and determinism passes:

• word-character-marker-default-refs: passes, confirming the control's one source site.
  … cut at 3000 characters; the whole file is runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.specify/contract.md

pr runtime/spec/pr.md

PR: #484

10 · ticket.specify · opening → completed 2026-10-06 05:20Z

11 · supervising → supervising 2026-10-06 05:04Z

12 · ticket.implement · implement → completed 2026-10-06 05:25Z

report runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.implement/report.md

{
  "summary": "Configured word-character markers now establish full-ID citation starts in the shared scanner, so unqualified spellings such as _FS_login produce one marked edge with their authored text and marker position for CLI and LSP consumers. Bare citations retain their word boundary, and ordinary missing-target checking receives the recovered edge.",
  "root_cause": "The leading word boundary in citation_re ran before marker detection and rejected IDs touching word-character markers, matching the supervisor's diagnosis.",
  "commits": [
    "369195ab742690d0f9a40b026fa346482a6f2674"
  ],
  "files": [
    "crates/grund-core/src/grammar/compiled.rs",
    "crates/grund-core/src/grammar/ids.rs",
    "crates/grund-core/src/grammar/comment_line.rs",
    "crates/grund-core/src/scanner/file_pass.rs",
    "panta/github-issues-agent-grounds-grund-483-implement-16045646/runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.implement/report.md",
    "panta/github-issues-agent-grounds-grund-483-implement-16045646/runtime/results/github-issues-agent-grounds-grund-483-implement-16045646.ticket.implement.md"
  ],
  "tests": [
    "word_character_marker_cli_contract",
    "word_character_marker_full_ids_keep_positions_and_sections",
    "word_character_marker_qualified_and_full_id_precedence_are_preserved",
    "word_character_marker_definition_after_emoji_uses_utf16_origin"
  ],
  "ci": {
    "rustfmt --edition 2024 crates/grund-core/src/grammar/compiled.rs crates/grund-core/src/grammar/ids.rs crates/grund-core/src/grammar/comment_line.rs crates/grund-core/src/scanner/file_pass.rs": "pass"
  },
… cut at 3000 characters; the whole file is runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.implement/report.md

</details>

<details><summary><b>13 · supervising → supervising</b> 2026-10-06 05:04Z</summary>

</details>

<details><summary><b>14 · ticket.review-1 · review → completed</b> 2026-10-06 05:31Z</summary>

_findings_ `runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.review-1/findings.md`

```json
{
  "round": 1,
  "verdict": "changes-requested",
  "findings": [
    {
      "id": "R1-01",
      "severity": "major",
      "category": "correctness",
      "file": "crates/grund-core/src/grammar/ids.rs",
      "line": 89,
      "summary": "A marker inside a valid bare full ID steals the enclosing citation and produces a false dangling suffix.",
      "repro": "Ran python panta/github-issues-agent-grounds-grund-483-implement-16045646/runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/review-1-edge-probes.py, exit 0; exact comparison is panta/github-issues-agent-grounds-grund-483-implement-16045646/runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/review-1-edge-probes.log. With strict=false, marker=\"-\", format=\"{kind}-{slug}\", slug_pattern=\"[A-Za-z0-9][A-Za-z0-9-]*\", declaration FS-login-FS-logout and source \"// see FS-login-FS-logout\", baseline af9f6f56d2 cover emits the one bare FS-login-FS-logout edge at column 8 and check exits 0 with \"success\". HEAD 369195ab74 cover instead emits only marked FS-logout at column 16, text \"-FS-logout\"; check exits 1 with \"src/lib.rs:1: error: unknown reference FS-logout\" and \"docs/functional-spec/FS-login.md:1: warning: declared but never cited: FS-login-FS-logout\". The same regression reproduces with marker=\"_\", format=\"{kind}_{slug}\", slug_pattern=\"[A-Za-z0-9][A-Za-z0-9_]*\", and FS_login_FS_logout: baseline success becomes unknown FS_logout. This change causes it: the marker-tail pass admits the internal suffix first, then lines 89-93 discard the earlier containing bare capture solely because their spans overlap.",
      "fix": "Preserve an enclosing valid full-ID token when merging candidates instead of unconditionally giving its internal marker suffix precedence; pin both marker variants in scanner and shared note-classification regression coverage.",
      "criterion": "Acceptance criterion 2 and FS-check.1.1.10: retain existing bare-token and full-ID behavior; the accepted compatibility correction recovers missed edges, rather than replacing previously valid edges."
    },
    {
      "id": "R1-02",
      "severity": "major",
      "category": "correctness",
      "file": "crates/grund-core/src/grammar/ids.rs",
      "line": 75,
      "summary": "Non-overlapping marker search still hides full-ID citations after an overlapping word-character marker.",
… cut at 3000 characters; the whole file is runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.review-1/findings.md

</details>

<details><summary><b>15 · supervising → supervising</b> 2026-10-06 05:04Z</summary>

</details>

<details><summary><b>16 · ticket.fix-1 · fix → completed</b> 2026-10-06 05:36Z</summary>

_resolutions_ `runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.fix-1/resolutions.md`

```json
{
  "round": 1,
  "resolutions": [
    {
      "id": "R1-01",
      "status": "fixed",
      "commit": "b6b8ed5db53a99acd2c12fd8b38af36969770aad",
      "note": "Grammar::citation_captures now collects the existing boundary-aware full-ID candidates before admitting marker-tail candidates, and declines an internal marked suffix when a full ID starts before its marker and contains its complete span. This preserves the enclosing bare token and the existing explicitly marked token ownership and deduplication in both shared consumers. Scanner regressions assert one intact FS-login-FS-logout or FS_login_FS_logout record at column 8, with exact text, no marker, and no checker errors or warnings; explicitly marked controls retain one whole-target record at column 4 under both strict modes. Shared note-classification regressions assert full-token ranges, no prose on pointer-only lines, and conforming citation-first layout with a note for both marker variants and an ordinary marked-ID deduplication control. Changed files: crates/grund-core/src/grammar/ids.rs, grammar/mod.rs, grammar/tests_word_character_marker.rs, and scanner/tests_word_character_marker.rs. Existing FS-check.1.1.10 already covers the remedy and is cited beside the behavior. Assertions were inspected but not run; no post-fix behavioral or CI success is claimed."
    },
    {
      "id": "R1-02",
      "status": "fixed",
      "commit": "b6b8ed5db53a99acd2c12fd8b38af36969770aad",
      "note": "The shared marker-tail search now visits character-boundary starts rather than non-overlapping match_indices occurrences, while retaining claimed-span suppression after a successful full-ID candidate. Scanner regressions require // ___FS_login to produce exactly one marked FS_login record, text __FS_login, column 5, and no checker errors or warnings. Exact __ and punctuation :: controls, both strict modes, an emoji prefix, and overlapping multibyte word marker éé pin deduplication and byte offsets. Shared note-classification tests assert the identical ranges and authored text. The same four files and commit contain this repair; all original CLI/scanner/LSP regressions, specification, compatibility decision, and release notice remain intact. Tests, builds, runtime probes, fissile, and the complete gate were intentionally unrun in this state; review-2 and green must verify the assertions."
    }
  ],
  "ci": {
    "rustfmt --edition 2024 --config skip_children=true crates/grund-core/src/grammar/ids.rs crates/grund-core/src/grammar/mod.rs crates/grund-core/src/grammar/tests_word_character_marker.rs crates/grund-core/src/scanner/tests_word_character_marker.rs": "pass",
    "git diff --check": "pass",
    "git diff --cached --check": "pass"
  }
}

17 · supervising → supervising 2026-10-06 05:04Z

18 · ticket.review-2 · review → completed 2026-10-06 05:42Z

findings runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.review-2/findings.md

{
  "round": 2,
  "verdict": "changes-requested",
  "findings": [
    {
      "id": "R2-01",
      "severity": "major",
      "category": "correctness",
      "file": "crates/grund-core/src/scanner/tests_word_character_marker.rs",
      "line": 177,
      "summary": "The new checker assertions require Debug on Diagnostic and prevent the core test target from compiling.",
      "repro": "Ran cargo test --workspace --locked --no-fail-fast --target-dir \"$HOME/ag/tmp/grund-issue-483-target\" word_character_marker -- --nocapture at b6b8ed5db53a99acd2c12fd8b38af36969770aad; exit 101. The compiler prints error[E0277]: `Diagnostic` doesn't implement `Debug` at scanner/tests_word_character_marker.rs:177:55, :178:57, :222:59, and :223:61, then error: could not compile `grund-core` (lib test) due to 4 previous errors. These are the four new assert!(report.errors/warnings.is_empty(), \"{:?}\", report.errors/warnings) calls. Diagnostic at crates/grund-core/src/model/report.rs:39 has no Debug implementation. Exact output: runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/review-2-tests.log under the task workspace. No core scanner or shared note-classification regression can execute on the committed change.",
      "fix": "Use assertion messages that can format the existing Diagnostic representation in all four calls, then rerun the focused workspace regressions and relevant core tests.",
      "criterion": "Acceptance criteria 4 and 6: repository regressions must pin the repair and the complete local gate must pass; the introduced compile failure prevents execution of both new scanner regressions and all core tests."
    }
  ]
}

19 · supervising → supervising 2026-10-06 05:04Z

20 · ticket.fix-2 · fix → completed 2026-10-06 05:45Z

resolutions runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.fix-2/resolutions.md

{
  "round": 2,
  "resolutions": [
    {
      "id": "R2-01",
      "status": "fixed",
      "commit": "95f163205b24ba8cc115df982065f0fbc4b1de43",
      "note": "Changed only the four checker assertion messages in crates/grund-core/src/scanner/tests_word_character_marker.rs to format collected references to diagnostic codes and messages, following the existing scanner-test pattern. These fields support Debug; Diagnostic itself is no longer formatted. All error/warning emptiness predicates, fixtures, positions, tokens, strict-mode coverage and range assertions are retained, grounded in §FS-check.1.1.10 docs/functional-spec/FS-check.md:119. No production behavior or diagnostic API changed. Formatting and unstaged/staged whitespace checks passed. Tests, builds, reproducer, fissile and the complete gate were not run, as the supervisor brief requires; compilation, behavioral verification and CI success remain unclaimed and must be established by green."
    }
  ],
  "ci": {
    "rustfmt --edition 2024 --config skip_children=true --check crates/grund-core/src/scanner/tests_word_character_marker.rs": "pass",
    "git diff --check": "pass",
    "git diff --cached --check": "pass",
    "python - (handoff JSON, finding coverage and result-file validation)": "pass"
  }
}

21 · supervising → supervising 2026-10-06 05:04Z

22 · ticket.green · green → completed 2026-10-06 05:55Z · `READY: yes`

green runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.green/green.md

The gate, run 1

Checkout /home/vjovanov/ag/grund/fix/issue-483 on fix/issue-483 at 95f163205b; 3 command(s) and the reproducer, 8m12s in all.

grund: the installed grund 0.15.1-dev, since the checkout pins none.

check	command	exit	time
reproducer	bash /home/vjovanov/ag/grund/fix/issue-483/panta/github-issues-agent-grounds-grund-483-implement-16045646/runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/run.sh	0	0m00s
1	cargo test --workspace --locked --no-fail-fast --target-dir "$HOME/ag/tmp/grund-issue-483-target" word_character_marker -- --nocapture	0	0m04s
2	pre-commit run --all-files	0	8m08s
3	fissile check --staged	0	0m00s

reproducer. bash /home/vjovanov/ag/grund/fix/issue-483/panta/github-issues-agent-grounds-grund-483-implement-16045646/runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/run.sh - passed

Verdict lines:

  grund check:
    success
expected: refs=1 cover=1 check=1 (the configured marker cites the declared FS_login, as '§' does)
observed: refs=1 cover=1 check=1
defect gone: underscore-marked citation is recognized

1. cargo test --workspace --locked --no-fail-fast --target-dir "$HOME/ag/tmp/grund-issue-483-target" word_character_marker -- --nocapture - passed

Verdict lines:

running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 7 filtered out; finished in 0.00s
     Running tests/workspace_resilience.rs (/home/vjovanov/ag/tmp/grund-issue-483-target/debug/deps/workspace_resilience-306649c87b5d9b77)
running 0 tests
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 4 filtered out; finished in 0.00s

2. pre-commit run --all-files - passed

Verdict lines:

grund fmt................................................................Passed
grund init --check (managed block is current)............................Passed
lychee...................................................................Passed
fissile (file size budgets)..............................................Passed
no Claude attribution boilerplate (staged files).........................Passed

3. fissile check --staged - passed

Verdict lines:

ok

READY: yes

23 · supervising → supervising 2026-10-06 05:04Z

24 · ticket.describe · describe → completed 2026-10-06 05:58Z

description runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.describe/description.md

{
  "title": "Recognize citations with word-character markers",
  "body_path": "runtime/supervision/pr-description.md",
  "ticket": "#483",
  "steps_summarized": 15,
  "accounting": "measured",
  "notes": ""
}

pr-description runtime/supervision/pr-description.md

Closes #483

With [reference] marker = "_" and [id] format = "{kind}_{slug}", the citation //! _FS_login previously disappeared from the citation graph even when FS_login was declared. It now behaves like the default-marker spelling:

Surface	Before	After
grund refs FS_login	Empty output	src/lib.rs:1: _FS_login
grund cover --format json	No citation for src/lib.rs	Exactly one marked FS_login citation, retaining _FS_login, line 1 and marker column 5
grund check	False declared but never cited warning	Recognizes the inbound citation; the valid fixture passes
LSP definition in //! 😀 _FS_login	null	Resolves from the marker or ID to the declaration, with the correct UTF-16 origin range

The configured marker now establishes the start of a full-ID citation without requiring a word boundary between marker and ID. The scanner and inline-note classifier share this recognition, preserving authored text and source positions; CLI queries, checking and editor navigation consume the recovered edge. The new recognition contract is §FS-check.1.1.10, with the shared detection design updated at §AR-scanner.2.3.

Both strict modes recognize the marked spelling. Bare IDs keep their ordinary word boundaries, and escapes, fenced examples, link destinations and assigned Python data keep their exclusions. An enclosing full ID retains ownership of internal marker-shaped suffixes, and full IDs retain precedence over shorthand. Overlapping starts are recognized too: with marker __, // ___FS_login produces one __FS_login citation at column 5. Qualified citations, section suffixes and multibyte positions remain covered by the same contract. §FS-check.1.1.10

The configuration specification explicitly permits word-character markers, and the editor specification pins definition navigation after a non-ASCII prefix and parity with CLI recognition. §FS-config.3.1, §FS-lsp.1.3, §FS-lsp.4

… cut at 3000 characters; the whole file is runtime/supervision/pr-description.md

25 · supervising → supervising 2026-10-06 05:04Z

26 · ticket.ship · ship → ship-fix 2026-10-06 05:59Z

shipped runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.ship/shipped.md

{
  "pr": 484,
  "url": "https://github.com/agent-grounds/grund/pull/484",
  "branch": "fix/issue-483",
  "merged": true,
  "merge_commit": "a31410b204e8c72d4c9c25b0f6dd901a6db0bf65",
  "ci": {
    "cargo test (ubuntu-latest)": "pass",
    "cargo test (macos-latest)": "pass",
    "cargo test (windows-latest)": "pass",
    "commit message attribution gate": "pass",
    "cargo bench (instruction counts)": "pass"
  },
  "fixups": [
    "Applied the release title Recognize citations with word-character markers"
  ],
  "main": {
    "commit": "a31410b204e8c72d4c9c25b0f6dd901a6db0bf65",
    "runs": {
      "CI": "success"
    },
    "status": "green"
  },
  "notes": "Merged as a31410b204e8c72d4c9c25b0f6dd901a6db0bf65; main is green on it (1 run(s))."
}

27 · ticket.ship · ship-fix → ship 2026-10-06 06:00Z

fix runtime/ship/github-issues-agent-grounds-grund-483-implement-16045646.ticket.ship/fix-1.md

Ship status requested the supervisor's manual preparation action. PR #484 still had the specification-stage title, Specify word-character citation marker recognition and regressions.

Applied the exported title through gh api repos/agent-grounds/grund/pulls/484 --method PATCH --input - with a structured JSON request. A separate REST readback verified the exact title and confirmed that the accepted body matches runtime/supervision/pr-description.md byte-for-byte, including its collapsed workflow snapshot. PR #484 remains an open draft at 95f1632.

No repository code changed and no commit or gate rerun was needed for this title-only action. No push, readiness change, CI wait, merge, or state transition was performed. Hosted checks, merge, and default-branch results remain unproven and belong to the ship program.

FIXUP: Applied the release title Recognize citations with word-character markers
SHIP: retry

28 · ticket.ship · ship → awaiting-checks 2026-10-06 05:59Z

29 · ticket.ship · awaiting-checks → merging 2026-10-06 06:01Z

30 · ticket.ship · merging → watching-main 2026-10-06 06:11Z

31 · ticket.ship · watching-main → completed 2026-10-06 06:11Z

Artifacts without a transition

run.sh runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/run.sh

#!/usr/bin/env bash

grund.57: an unqualified citation written with a word-character marker

([reference] marker = "_", so _FS_login) is invisible to refs and cover.

Run from the grund checkout. exit 1 = defect stands, 0 = gone, 2 = could not run.

set -uo pipefail

[ -f Cargo.toml ] && grep -q 'crates/grund-cli' Cargo.toml
|| { echo "run.sh: run me from a grund checkout" >&2; exit 2; }

mkdir -p "$HOME/ag/tmp" || exit 2
target="$HOME/ag/tmp/grund-issue-483-target"
cargo build -q -p grund --target-dir "$target" >&2
|| { echo "run.sh: cargo build failed" >&2; exit 2; }
grund="$target/debug/grund"
echo "grund: $("$grund" --version) at $(git rev-parse HEAD 2>/dev/null || echo unknown)"

work="$(mktemp -d "$HOME/ag/tmp/grund-issue-483.XXXXXX")" || { echo "run.sh: mktemp failed" >&2; exit 2; }
trap 'rm -rf "$work"' EXIT

fixture

fixture() {
mkdir -p "$1/docs/functional-spec" "$1/src"
printf 'grund_config_version = 1\n\n[id]\nformat = "{kind}_{slug}"\n\n[reference]\nmarker = "%s"\n\n[fmt.cross_refs]\nenabled = false\n' "$2" > "$1/grund.toml"
printf '\n[[kinds]]\nkind = "FS"\nfolder = "docs/functional-spec"\nindex = false\n' >> "$1/grund.toml"
printf '# FS_login: Login\n\nLead.\n' > "$1/docs/functional-spec/FS-login.md"
printf '//! %sFS_login\n' "$2" > "$1/src/lib.rs"
}

probe : prints "refs=<0|1> cover=<0|1>" (1 = citation seen)

probe() {
local refs cover check
refs="$(cd "$1" && "$grund" refs FS_login 2>&1)" || { echo "$refs" >&2; exit 2; }
cover="$(cd "$1" && "$grund" cover --format json 2>&1)" || { echo "$cover" >&2; exit 2; }
check="$(cd "$1" && "$grund" check 2>&1)" || { echo "$check" >&2; exit 2; }
echo " grund refs FS_login:" ; sed 's/^/ /' <<<"$refs"
echo " grund cover --format json:" ; sed 's/^/ /' <<<"$cover"
echo " grund check:"; sed 's/^/ /' <<<"$check"
local r=0 c=0 k=0
grep -q '^src/lib.rs:1:' <<<"$refs" && r=1
grep -q '"path":"src/lib.rs","citations":[{.*"id":"FS_login"' <<<"$cover" && c=1
grep -qx 'success' <<<"$check" && k=1
PROBE="refs=$r cover=$c check=$k"
}

fixture "$work/control" '§'
echo "control, marker '§', src/lib.rs = '//! §FS_login':"
probe "$work/control"; control="$PROBE"
if [ "$control" != "refs=1 cover=1 check=1" ]; then
echo "run.sh: control with marker '§' did not see the citation ($control); fixture broken" >&2
exit 2
fi

fixture "$work/under" ''
echo "subject, marker '', src/lib.rs = '//! _FS_login':"
probe "$work/under"; subject="$PROBE"

echo "expected: refs=1 cover=1 check=1 (the configured marker cites the declared FS_login, as '§' does)"
echo "observed: $subject"
if [ "$subject" = "refs=1 cover=1 check=1" ]; then
echo "defect gone: underscore-marked citation is recognized"
exit 0
fi
echo "defect stands: underscore-marked unqualified citation is invisible (citation_re's \b before the ID)"
exit 1

run.log runtime/repro/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/run.log

grund: grund 0.16.2-dev at af9f6f5
control, marker '§', src/lib.rs = '//! §FS_login':
grund refs FS_login:
src/lib.rs:1: §FS_login
grund cover --format json:
{"path":"docs/functional-spec/FS-login.md","citations":[]}
{"path":"src/lib.rs","citations":[{"path":"src/lib.rs","line":1,"column":5,"id":"FS_login","section":null,"marker":true,"text":"§FS_login","enclosing_declaration":null,"enclosing_section":null}]}
grund check:
success
subject, marker '_', src/lib.rs = '//! _FS_login':
grund refs FS_login:

grund cover --format json:
{"path":"docs/functional-spec/FS-login.md","citations":[]}
{"path":"src/lib.rs","citations":[]}
grund check:
docs/functional-spec/FS-login.md:1: warning: declared but never cited: FS_login
expected: refs=1 cover=1 check=1 (the configured marker cites the declared FS_login, as '§' does)
observed: refs=0 cover=0 check=0
defect stands: underscore-marked unqualified citation is invisible (citation_re's \b before the ID)

Outcome completed · Verdict: shipped - #484 merged as a31410b.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage · Validated: kind bug, verdict none. The export is runtime/exports/github-issues-agent-grounds-grund-483-implement-16045646.ticket.triage/validation.md.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.clarify · Simple path: existing reproduction and configured-marker promise settle the ask; no author question remains.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.plan · Simple path: repair restores existing citation recognition; the supervisor Approach supplies the implementation scope.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.dependencies · Simple path: no approved proposal or prerequisite ticket is required for this shared-scanner repair.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.agora · Simple path: existing ground agrees on configured-marker recognition; no foundational ruling is needed.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.specify · Draft pull request #484 opened from fix/issue-483 with the specification change and the failing test.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.implement · Implemented and committed shared full-ID recognition after word-character citation markers in 369195a.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.review-1 · Changes requested: 2 major findings; 0 blocker, minor, nit, or adjacent findings.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.fix-1 · Fixed R1-01 and R1-02 in shared citation candidate selection and added regressions; broader changes were excluded and behavioral verification remains unrun for review-2 and green.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.review-2 · Changes requested: 1 major finding; 0 blocker, minor, nit, or adjacent findings; both round-1 counterexamples are verified resolved.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.fix-2 · Fixed R2-01's four scanner-test assertion messages; no production behavior changed, and compilation and behavioral validation remain pending for green.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.green · The gate is green: 3 command(s) and the reproducer passed on 95f1632 in 8m12s.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.describe · Suggested title: Recognize citations with word-character markers.

Outcome github-issues-agent-grounds-grund-483-implement-16045646.ticket.ship · Pull request #484 merged as a31410b.

Rendered from github-issues-agent-grounds-grund-483-implement-16045646/tasks/01-ticket.md by scripts/lifecycle-sync.sh.

[vjovanov]

Claimed by vjovanov@kung-fu-workstation on 2026-10-06 05:02Z · released on 2026-10-06 06:38Z (completed).