7 Commits

Author	SHA1	Message	Date
Zenflow	c22ebbe45c	New task (zenflow 738246ea) ... In the Pairing Simulator page, I am getting the error: **Error:**Unexpected token '<', "<!DOCTYPE "... is not valid JSON Fid and fix the bug	2026-03-11 13:02:24 -05:00
jason	389636ce6f	fix: COI correctly calculates parent×offspring and direct-relation pairings ... - Remove blanket `id !== sid && id !== did` exclusion from commonIds filter which was silently zeroing out COI for parent×offspring pairings because the sire (sid) IS the common ancestor in damMap but was being filtered out. - Instead: exclude `did` from sireMap keys (sire can't be its own common ancestor with the dam) and exclude `sid` from damMap keys (same logic). - Parent×offspring pairing now correctly yields ~25% COI as expected by Wright's path coefficient method. - All other normal pairings are unaffected.	2026-03-10 15:08:33 -05:00
jason	2164b035a8	fix(backend): move named routes above /:id wildcard — Express route order bug causing 0% COI	2026-03-10 15:01:22 -05:00
jason	c949fe2502	fix(backend): rewrite COI with self-at-gen-0 Wright method + direct-relation detection endpoint	2026-03-10 14:54:59 -05:00
jason	f5ee9837c6	fix: correct COI Wright path algorithm — include sire/dam as direct ancestors of each other	2026-03-10 14:44:27 -05:00
jason	20fcc39a58	fix: use single quotes for sex string literals in trial-pairing SQL (SQLite double-quote = identifier)	2026-03-10 14:38:16 -05:00
jason	df252e828a	Add pedigree API routes	2026-03-08 22:45:07 -05:00