Exercise 3: Two Genuinely Express-Specific Findings — Possible Solution
====================================================================

FINDING ONE: THE RECURSIVE CTE (CHAPTER 6)
------------------------------
Per this chapter, Chapter 6's WITH RECURSIVE query resolves the full
ancestor chain for a page in one query, genuinely unbounded in depth
- verified concretely against a six-level-deep tree resolved by the
exact same unchanged query used for three levels. This is grounded
in a real, verifiable fact: this course has no ORM layer sitting
between the application code and the database, so nothing prevented
reaching directly for MySQL 8's own real recursive common table
expression support, the theoretical fix five sibling ORMs each named
but never actually built.

FINDING TWO: requireAuth AS REAL STRUCTURE, NOT AN ABSENCE (CHAPTER 9)
------------------------------
Per this chapter, Express provides no specific authentication
middleware, but it does provide a real, general-purpose extensibility
mechanism - the (req, res, next) middleware function signature -
used in Chapter 9 to build requireAuth. This is grounded in a real,
verifiable fact about Express's own architecture: middleware
functions are Express's own standard, first-class mechanism for
every cross-cutting concern (parsing, logging, sessions), not a
workaround improvised because nothing else existed.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly names two findings unique to Express among the six
frameworks, and correctly grounds each one in a specific, verifiable
technical fact - the total absence of an ORM layer enabling the
recursive CTE, and Express's own real middleware architecture
underlying requireAuth - rather than restating a similarity Express
already shares with a sibling elsewhere in the course.