Rewrite Python comments in Google developer documentation style (#12)

* Rewrite comments in Google developer documentation style

Rewrite the comments and docstrings across the backend core modules so they
read plainly. The previous prose was accurate but dense and figurative, which
made it slow to skim.

Applies the Google developer documentation style guide: short sentences, active
voice, present tense, American spelling, and no metaphors, idioms, or
rhetorical asides. Replaces em-dash chains with separate sentences.

backend/app/scripting/engine.py

@@ -94,8 +94,9 @@ def run_hook(
     story_cards: list[dict],
     info: dict,
 ) -> HookResult:
-    """Run one modifier hook. Never raises: failures come back as .error with
-    text/state/cards unchanged, so a bad script can't break a turn."""
+    """Run one modifier hook. This function never raises. Failures return as
+    `.error` with text, state, and cards unchanged, so a bad script cannot
+    break a turn."""
     unchanged = HookResult(text=text, state=state, story_cards=story_cards)
     source = f"{library_js}\n;\n{hook_js}" if library_js.strip() else hook_js
     if not source.strip():

backend/app/scripting/pipeline.py

@@ -24,19 +24,20 @@ class ScriptPipeline:
         return msg if isinstance(msg, str) and msg.strip() else None
 
     def _history(self) -> list[dict]:
-        # The path, not `adventure.actions` — that collection is every branch's
-        # actions, and this is the documented history API a user script reads.
-        # Handing a script the siblings of the turn it is running on would be
-        # the same bug as building a prompt from them, only user-visible.
+        # Read the path rather than `adventure.actions`. That collection holds
+        # every branch's actions, and this is the documented history API a user
+        # script reads. Giving a script the siblings of the turn it is running on
+        # would be the same bug as building a prompt from them, and visible to
+        # the user.
         #
-        # `story_actions` also drops blank-text rows, which `adventure.actions`
-        # kept, so this array is shorter than it used to be for an adventure
-        # that has any — and `info.actionCount` counts the same way. That is
-        # deliberate: a row with no text is this app's bookkeeping, it has no
-        # counterpart in the AI Dungeon history a ported script was written
-        # against, and the prompt has never included one. A script keyed on
-        # "every N actions" will land on different turns than it did before
-        # phase 14; there is no reading of this that is compatible with both.
+        # `story_actions` also drops rows with blank text, which
+        # `adventure.actions` kept, so this array is shorter than it was for an
+        # adventure that has any such rows. `info.actionCount` counts the same
+        # way. That is intended. A row with no text is this app's bookkeeping, it
+        # has no counterpart in the AI Dungeon history a ported script was
+        # written against, and the prompt has never included one. A script keyed
+        # on every N actions lands on different turns than it did before phase
+        # 14, and no reading of this is compatible with both.
         return [
             {"text": a.text, "rawText": a.text, "type": a.type}
             for a in context_history.story_actions(self.adventure)