[lesnik512]

The broker.publish signature on the publisher page was missing timer_conflict, added in 0.19.0 (#254). Its returns line also said None only means a timer_id conflict made the insert a no-op. With "extend", None instead means a worker has already claimed the timer.

This adds the argument to the signature and explains what each mode returns, linking to the timers page for the details. just docs-build passes in strict mode.

[github-actions]

Benchmark gate

✅ gate passed

scenario	msg/s	delete/msg	WALrec/msg	WALB/msg	fpi	upd	del	dead_tup
consumer/w1/b10	1332	1.000	6.71	920	242	5000	5000	10000
consumer/w1/b100	1442	1.000	7.11	1154	243	5000	5000	10000
consumer/w2/b10	1565	1.000	6.72	923	242	5000	5000	10000
consumer/w2/b100	1810	1.000	7.11	1154	243	5000	5000	10000
consumer/w4/b10	1616	1.000	6.73	949	242	5000	5000	10000
consumer/w4/b100	1874	1.000	7.11	1153	243	5000	5000	10000
consumer/w1/b100/tfbs100	5466	0.010	6.17	1173	265	5000	5000	10000
consumer/w1/b100/interval1-10	1450	1.000	7.11	1155	243	5000	5000	10000
producer/w1/b100	2977	0.000	3.04	597	1	0	0	0
producer/w1/b100/ppt1	959	0.000	4.04	635	0	0	0	0

Gated (fails the build): delete_calls + tuple counters (upd/del/ins) + the producer's insert_calls, exact; select_calls and other_calls within +2; wal_records within a 10% band; fetch_calls within 2x. msg/s, WAL bytes and total calls are informational (timing/FPI noise).