How does the toxcore work，is there a brief and complete description about how does it work in detail?

After reading the doc "DHT protocol", "Tox-Docs/Text",and even "bep_0005", I know a lot about the toxcore's run mode, but it's still very hard to get a comprehensive description in my mind. I think, a comprehensive description in brief and friendly to an ordinary/advanced users is necessary.

Here is what confused me:

1. in "DHT protocol",it mentioned ""friends" list", it stors 8 clients' "information"(i.e. ip addresses + port + node_id + timestamp of the friend) closest to each "friend",does it store the friends' "information"(same as above) .

2. in "Tox-Docs/Text",it mentioned "onion model",but i don't know if has it been implemented by the toxcore(and is Tox-Docs reliable,i.e. things mentioned in it is just in working and absolutely not done?!). in "bep_0005", it has the concept "node" and "peer". so:

   2.1 dose toxcore creat a new id(?or called peer_id or chat_id? infact,a key-pair's pub key) when an user startup a client program and just for this conversation? if it does,how does it work between node_id and the new id? if it created,but not just for this conversation,does toxcore's route table (inluding the "clent list" and/or ""friends" list" said in "DHT protocol") is base on the newly created id(?or called peer_id?) or not?

   2.2 dose toxcore chat with a friend on a "onion model" by defalt(i.e. not directly to his friend but through a random first jump and jump sevral times to his friend) if it does,how does it work? if it doesn't,how does it work?

3. it seems that the "Toxcore todo list." doesn't sync.

where could i get a brief and complete description about how does it work in detail?

Could the "README.md" include a "DidLst!" that well sync? and a "A brief and complete description about how does it work in detail!"