Context Navigation

Changes between Version 1 and Version 2 of Ticket #64596, comment 15

v1	v2
56	56	Post Abilities was the concrete visualization that caused the team to push forward the approach, This is an enhancement in and of itself that we plan to use for most - if not all - complex abilities.
57	57
58		We cannot test or iterate on essential Core abilities ''outside of core'' (e.g. in the Experiments plugin for feedback) that would benefit from slug fragments without nested abilities being in core (the other solutions I came up with add a significant amount of tech-debt, like a hook to short-circuit the registry validation - which compromises the schema integrity of Abilities (it's entire raison d'etre).
	58	We cannot test or iterate on essential Core abilities ''outside of core'' (e.g. in the Experiments plugin for feedback) that would benefit from slug fragments without nested abilities being in core (the other solutions I came up with add a significant amount of tech-debt, like a hook to short-circuit the registry validation - which compromises the schema integrity of Abilities, it's entire raison d'etre).
59	59
60	60	And we obviously don't want to ship a bunch of subpar `core/{verb}-{post-type}` to core to only then have to deprecate and cause the actual futurecompat friction we both agree is important to avoid.