Track guessed as P from the test source. The ranker reads frontmatter, so this line — not the body — decides who works it; correct it if the guess is wrong.

origin/master has advanced 2 commit(s) since this sha. Re-verify at current HEAD before acting — the callback is tagged to the sha that was tested, which may no longer be the state of the tree.

regression: test-core#src:test/test_object_reference.pas red at f9bfcca97409 (auto-filed by twatch)

• Type: regression (auto-filed by Track T watcher, host seven). Untriaged.
• Found: 2026-08-30T08:27:45Z
• Test source: test/test_object_reference.pas tools/expect_same.sh +1

Repro

tools/testmgr.py --tier native --job 'test-core#src:test/test_object_reference.pas' at f9bfcca974096943df450d704785adc4955fa938

Range

The named sha f9bfcca97409 CANNOT be the cause — it touches no buildable file (docs / tickets / tstate only). It is the sha that was TESTED, i.e. the upper bound of an untested range; the cause is somewhere below it.

bad f9bfcca97409, last good 8fbee6e13141, 6 commit(s) in range — the watcher narrows this by idle bisect; check tstate/TSTATE.md for the current range.

Log tail

ok: /tmp/testmgr-scratch-1633264/test_object_reference26  [code=65304B  data=4276B  bss=42532B  procs=134]

Stub ticket: signal only. Track T agent (face 2) enriches or a dev track takes it from the repro line.

Log

• 2026-08-30 — auto-closed by the seven watcher: test-core#src:test/test_object_reference.pas passes at 5c3c0b74bf2c (tier native); it was red at f9bfcca97409. Reopening is by a fresh NEW-RED stub, since a second red is a second finding with its own range.