nx_jobfollow_parse.nx

nx_jobfollow_parse.nx -- THE PURE HALF of the job-pointer follower: parsing and buffer arithmetic, with NO transport dependency at all. WHY IT IS A SEPARATE FILE. The follower has to live in TWO places: nx_jobfollow_lib (which an explicit caller composes) and nx_https_post_lib (so that EVERY caller of hp_post_json inherits it without editing 81 organs). But nx_jobfollow_lib imports nx_https_post_lib to do its polling, so putting the follow INTO the post lib would close an import cycle. Splitting the pure half out is the standard break: this file imports only nx_syscalls, so both layers above can share ONE implementation and there is still exactly one job-id parser in the estate. AND THE PURE HALF IS THE HALF WORTH GATING. Everything here is buffer arithmetic over inputs a test can construct, so a gate walks it without opening a socket -- the same reason the TLS fragmentation split was pulled out of its loop on the same day. THE ANCHORED PARSE IS THE POINT. jf_job_id matches the whole literal `JOB-STARTED id=`, never a bare `id=`. MEASURED 2026-09-04: a client scanning unanchored read the JOB id as the ORGAN id -- they are both epoch-derived, so 1788537161 looked like a plausible prefix of the real 1788537161795845 -- and then reported a receipt that never existed. license_tier: ORIGINAL No hw writes (Rule 26).