Exercise 1: Why the Core REST API Stays Compatible, and Why That's Not Guaranteed Forever — Possible Solution
====================================================================

WHY THE CORE API REMAINS LARGELY COMPATIBLE
------------------------------
Per this chapter, "the core REST API surface remains largely
compatible for basic operations — indexing documents, basic search,
basic aggregations — a real, practical consequence of both projects
sharing the same starting codebase." Per search1-2's own material,
OpenSearch began as a literal fork of "the last Apache 2.0-licensed
version of Elasticsearch and Kibana" — meaning both projects started
from IDENTICAL code at the moment of the fork. Anything that already
existed in that shared starting codebase — including the fundamental
REST endpoints for indexing and searching documents — is, by
definition, present and working near-identically in both projects,
since neither project has had any reason to rewrite that already-
working, shared foundation from scratch independently.

WHY THIS COMPATIBILITY ISN'T GUARANTEED TO REMAIN COMPLETE OR
PERMANENT
------------------------------
Per this chapter, "since the fork, each project has developed its own
features independently, on separate release cycles, without the
other — over time, this means some newer functionality genuinely
exists in only one of the two, not both." The shared starting
codebase is a fixed, frozen snapshot from the moment of the 2021 fork
— everything built AFTER that point has been developed by each
project's own separate team, on its own separate schedule, without
coordination between the two. There's no ongoing mechanism keeping
the two projects synchronized going forward; the compatibility that
exists today reflects a shared PAST, not a coordinated present or
future. As each project continues adding its own new features,
changing existing behavior, or evolving its own API surface
independently, the amount of genuinely shared, identical functionality
can only shrink over time relative to each project's own total,
growing feature set — never guaranteed to stay complete.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains the compatibility as a direct, structural consequence of
the shared 2021 fork point (per search1-2's own material), and
explains precisely why that shared origin doesn't imply any ongoing
coordination or guarantee of continued compatibility, since each
project has developed independently ever since.