Exercise 3: What add_action('init', 'register_portfolio_post_type') Is Actually Doing — Possible Solution
====================================================================

WHAT THIS LINE OF CODE ACTUALLY DOES, MECHANICALLY
------------------------------
Per this chapter, add_action( 'hook_name', 'function_to_run' ) tells
WordPress to "call your function at the exact moment it reaches that
named point in its own execution." In this specific case, the hook
name is 'init' and the function is register_portfolio_post_type - so
this line registers register_portfolio_post_type as a function
WordPress should call the moment its own execution reaches the 'init'
action point, which fires once during every WordPress page load, early
in its own startup process.

WHY THIS EXPLAINS WHY register_post_type() ITSELF ISN'T CALLED DIRECTLY
------------------------------
Rather than calling register_post_type() directly at the top level of
a PHP file (which would run immediately when the file is parsed,
potentially before WordPress has finished its own internal setup),
wrapping it inside a function and hooking that function to init ensures
it runs at the correct, safe moment in WordPress's own lifecycle -
after enough of WordPress's own core has already loaded, but still
early enough in every single request for the post type to be properly
registered before anything else needs it.

WHY THIS IS THE SAME MECHANISM AS THE REST OF THIS CHAPTER'S OWN EXAMPLES
------------------------------
Per this chapter's own compare table, actions "let you DO something at
a specific point," with the hooked function's return value ignored.
register_portfolio_post_type doesn't return anything meaningful and
isn't expected to - it simply performs an action (registering the post
type) at the right moment, exactly matching the action pattern this
chapter formalized, rather than the filter pattern (which would require
returning a modified value).

WHY THIS RETROACTIVELY EXPLAINS WORDPRESS INTERMEDIATE/ADVANCED 4's OWN CODE
------------------------------
When this exact line first appeared in Chapter 4, it was used without
full explanation of what add_action() and 'init' actually meant. Now,
having covered the action/filter mechanism formally, that same code can
be read precisely: it's an ordinary instance of the action-hooking
pattern, running register_portfolio_post_type() at WordPress's own
'init' point every time a page loads, ensuring the custom post type is
always properly registered before it's needed.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains precisely what the hook call does mechanically using this
chapter's own action definition, explains why the registration is
wrapped in a hooked function rather than called directly, and explicitly
closes the loop back to where this exact code first appeared
unexplained in Chapter 4.