Rewatch Schedule Optimizer & Dual-Galaxy Trajectory Engine
The bundled episode database contains seventeen records tagged essential with durations totaling five hundred ninety one minutes. The Peridea route contains thirteen totaling five hundred eleven. Bars span two hundred six point eight five and one hundred seventy eight point eight five at point three five pixels per minute. Five hundred ninety one minutes is nine hours fifty one minutes, but the display rounds minutes divided by sixty and separately keeps the remainder, producing ten hours fifty one. Five hundred eleven similarly displays nine hours thirty one instead of eight hours thirty one. Durations and route choices are author fixture data, not verified runtime catalog evidence. The hard coded January twentieth twenty twenty seven target is an unverified source assumption, not a confirmed premiere announcement. Schedule generation puts the first episode on the chosen start date, then advances by a fixed interval. Seventeen episodes therefore span sixteen intervals. At seven days each, the last date is one hundred twelve days after the start; at three point five days, it is fifty six. Bars span one hundred sixty eight and eighty four at one point five pixels per day. Automatic pacing divides days until the assumed premiere by episode count. With an illustrative one hundred days available and seventeen episodes, the last starts after sixteen seventeenths of that window, about ninety four point one two days, leaving one interval unused. Fractional-day arithmetic and local date formatting are separate from verified broadcast scheduling. This source binds route, start date, velocity and export listeners before its initial D3 galaxy map call. If D3 is unavailable offline, the map throws before the initial schedule is calculated. Later native route changes can still invoke the already bound scheduling function and produce episode rows, and actual calendar or JSON exports can be checked independently. The bars compare seventeen essential records and thirteen Peridea records at twelve pixels per count. JSON reports a watched set size that can include other routes, whereas rendered progress counts only checked items in the current route. That distinction matters when interpreting progress. No countdown, fictional character location, external date claim or sample video establishes official canon or public completion.