Context Navigation

Changes between Version 2 and Version 3 of Ticket #36075

v2	v3
1	1	A particular focus should be put on the fact that the flag will and should only be set to `True` if the field is the single member of the primary key. When a composite primary is defined on the model this flag will be `False` for all the fields defined on the model and `_meta.pk_fields` (which should be documented) should be used instead to build composite primary key ready third-party application.
2	2
3		In other words, it should be made clear that code that relies solely on `Field.primary_key` is not composite primary key ready and that `_meta.pk_fields` should be used instead. I feel like this is something that should be clearly pointed out in the ~~release notes as well~~.
	3	In other words, it should be made clear that code that relies solely on `Field.primary_key` is not composite primary key ready and that `_meta.pk_fields` should be used instead. I feel like this is something that should be clearly pointed out in the composite primary key documentation on how to make reusable app code composite primary key ready.