The DIR655 would get an IPv6 Network assignment of 2601:5:c80:90::/60, and its LAN would get the IPv6 assignment 2601:5:c80:91::/64. Unfortunately I did not get a screen capture of the secondary router's assignment, but as I recall it was 2601:5:c80:92::/64.
Now that I only get a /64 assignment, I get the same 2601:5:c80:90::/64 for both the Network and LAN.
My secondary (guest network) router is now connected directly (well, actually through a switch), to the modem and it still gets its own /64 assignment (it's just not a subnet of the DIR655's former /60 network).
One interesting thing is that just before I stopped getting the /60 assignment, Comcast changed the Network PD IP address from 2601:5:c80:90::/60 to 2601:5:c80:b0::/60. The next change was to eliminate the /60 assignment (but I went back to the 2601:5:c80:90: subnet again).
I guess that the point of this TLDR reply is to point out that Comcast's IPv6 implementation for dynamic IP address customers is still in flux (and may possibly stay that way), so even if you get something to work today, don't count on it to be working the same way tomorrow. If/when Comcast finally gets IPv6 for static IP business class customers working, I may go back to paying for static IP addresses again.
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
When governments fear people, there is liberty. When the people fear the government, there is tyranny.