Checkpoint 1: implement native subsystems and begin the gameplay manual

docs/manual/scripting/index.md

@@ -0,0 +1,41 @@
+# C++ gameplay
+
+In the first version of Faset, a "script" is C++ gameplay code compiled into your game.
+It is not an interpreted text file. The gameplay library is statically linked into
+a separate Player executable.
+
+The intended iteration cycle is:
+
+1. Stop Play.
+2. Edit your C++ behavior or system.
+3. Build the changed code and export its property schema.
+4. Start a new Player session.
+
+The Editor reads a schema generated by a separate SchemaExporter. It does not load
+your gameplay library into its own process. A gameplay crash therefore does not
+automatically crash the Editor. Editor native extensions have a different lifecycle
+and run inside the Editor process.
+
+!!! note "API examples are added with implementation"
+    This page describes the accepted execution model. Exact function signatures and
+    complete examples will be documented alongside compiling runtime examples, rather
+    than presenting proposed APIs as available functions.
+
+## Behaviors and systems
+
+A behavior gives an individual object lifecycle callbacks. A system operates on a
+set of objects with matching components. Both use the same runtime state; the visual
+scene and Inspector are the authoring view of that state.
+
+Persistent scene IDs and runtime handles are different. A scene ID survives saving
+and reopening. A runtime handle belongs to a particular world/session and can become
+invalid after an object is removed. Do not store raw component pointers across
+structural changes or treat a runtime handle as a save-file ID.
+
+## Physics ownership
+
+Physics owns the position of a dynamic rigid body. Move it with the supported physics
+commands instead of writing its presentation transform. A camera or other visual-only
+object can follow the interpolated result without modifying the simulation.
+
+Continue with [Frame and physics updates](lifecycle.md).

docs/manual/scripting/lifecycle.md

@@ -0,0 +1,47 @@
+# Frame and physics updates
+
+!!! note "Execution contract"
+    This page describes the accepted runtime contract. The runnable callback examples
+    and test results are added as the runtime implementation becomes available.
+
+## Choose the right callback
+
+- `OnStart`: initialize a behavior once its object and components exist.
+- `FixedUpdate`: update simulation logic before a physics step.
+- `Update`: run frame-based gameplay once per rendered frame.
+- `LateUpdate`: update cameras and dependent visual objects after presentation interpolation.
+- `OnDestroy`: release subscriptions and other behavior-owned state before its handle is invalidated.
+
+The default simulation interval is 1/60 second. A rendered frame may contain zero,
+one, or several fixed ticks. Frame rate and physics rate are not the same quantity.
+
+## Fixed tick order
+
+1. Apply structural commands queued by earlier work.
+2. Deliver tick input and call `FixedUpdate`.
+3. Apply physics commands and step the 2D and 3D worlds.
+4. Read back transforms and queue collision events.
+5. Run reactions after physics.
+
+Object creation/removal and component addition/removal are deferred to the beginning
+of the next fixed tick. This prevents a callback from invalidating the collection
+currently being processed. New objects follow the same initialization rules as objects
+loaded from a scene.
+
+After the fixed ticks, the frame runs `Update`, prepares interpolated presentation
+transforms, calls `LateUpdate`, and produces the render snapshot.
+
+## Avoid frame-rate-dependent movement
+
+A speed is a distance per second. Multiply it by the callback's elapsed seconds when
+calculating a displacement. Do not multiply a velocity by elapsed time before assigning
+it to a physics velocity API; the physics step performs that integration.
+
+## Overload and pause
+
+The initial catch-up limit is four fixed ticks per frame. Excess whole intervals are
+dropped with a diagnostic rather than making the physics step arbitrarily large.
+This is a local-game policy, not a guarantee of deterministic network simulation.
+
+Pausing clears accumulated time. Single-step advances exactly one simulation tick.
+Interpolation history is reset for a new session, spawn, or teleport.