The repo is public and undiscoverable

[sylvioCampos]

The repository has an empty description and zero topics. For a repo whose entire purpose is being found and read, that is the binding constraint — nobody arrives by accident.

Cheap and immediate

• A one-line description. Something like: A FIX 4.4 session boilerplate in Go, built around a fake exchange you can command. Learn sequence gaps, resends and stuck sessions with curl.
• Topics: fix-protocol, fix44, quickfix, quickfixgo, golang, b3, trading, market-data, financial-information-exchange

The part that actually matters

Two things in this repo do not exist anywhere else public, and neither is discoverable from the outside:

1. quickfixgo has no per-session disconnect. The session type is unexported, and Initiator.Stop() unregisters every session it owns, so Start() afterwards leaves them unroutable. Anyone arriving from QuickFIX/J goes looking for Session.disconnect(reason, true) and finds nothing. The workaround — rebuild the Initiator, one session per Initiator — is in internal/session/supervisor.go and is not obvious.

2. The silent session. A session logged on with heartbeats flowing and no business data arriving passes every liveness check FIX has. Detecting it is the application layer's job and nothing in the ecosystem says so. That is drill 09.

Both are currently buried in the README and in docs/drills/09. Someone hitting either problem is searching for the symptom, not for this repo.

Worth a short write-up that leads with the symptom and links here. That is outside the repository itself, but it is the step that determines whether any of this gets read.

Acceptance

• Description and topics set
• A decision recorded on whether the write-up happens (doing it, or explicitly not)

[sylvioCampos]

Progress: the metadata half is done, the write-up half is not.

Done

• Description set: "A FIX 4.4 session boilerplate in Go, built around a fake exchange you can command. Learn sequence gaps, resends and stuck sessions with curl."
• Homepage pointed at the README
• 15 topics: fix-protocol, fix44, quickfix, quickfixgo, golang, go, b3, trading, fintech, financial-information-exchange, drop-copy, order-entry, market-infrastructure, teaching, boilerplate
• Wiki and Projects disabled, Issues on
• v0.1.0 released, so the repo no longer looks like an unreleased work in progress
• README badges for build, coverage, Go version, release, pinned quickfixgo version and licence

Still open — the part that actually matters

The findings remain discoverable only by already being in this repository, which is the wrong way round. Someone hitting these problems is searching for the symptom, not for a lab.

The list has grown since this issue was filed. Every one of these was found the hard way here, and none of them is documented anywhere public:

1. Settings.SessionSettings() returns clones — mutating them is a silent no-op
2. No per-session disconnect exists; Initiator.Stop() unregisters everything it owns
3. A session can be logged on with heartbeats flowing and deliver nothing, and no engine will tell you
4. Never reject a reject — two applications that both reject unknown types will ping-pong 35=j at wire speed
5. Rejects split by reject reason, not severity: an out-of-range value gives 35=3, a missing conditionally-required field on the same message gives 35=j
6. The message stores carry no synchronisation; reading a sequence number from another goroutine is a data race
7. Stock FIX 4.4 has no Text on Logon, so a venue that sends one gets dropped before OnLogon fires — nothing in the application log explains it

Next step: a symptom-led write-up covering these, drafted in-repo so it stays versioned with the code that proves each claim, and syndicated from there.