chore: synced pact-plugins docs

Author: Github Action

website/docs/implementation_guides/pact_plugins/docs/proposals/proposal_007_driver_plugin_callback_model.md

@@ -227,10 +227,22 @@ between gRPC, WASM, and Lua. Only the transport differs.
 
 This proposal ships as one vertical slice through the mechanism, not the full capability surface:
 
-1. The registry/trait pattern (`core_capabilities` module, generalising `PluginLogSink`).
-2. The extended `PluginHost` gRPC service with cycle detection and deadline propagation.
-3. Wiring the two existing `is_core()` branches in `content.rs` to call through instead of panicking.
+1. ✅ The registry/trait pattern (`core_capabilities` module, generalising `PluginLogSink`). Done in both
+   drivers: Rust (`core_capabilities.rs`) and JVM (`CoreCapabilities.kt`).
+2. ✅ The extended `PluginHost` gRPC service with cycle detection and deadline propagation. Done in both
+   drivers: Rust (`call_chain.rs`, `plugin_host.rs`) and JVM (`CallChain.kt`, `PluginHostServer.kt`).
+3. ✅ Wiring the two existing `is_core()` branches in `content.rs` to call through instead of panicking. Done in
+   both drivers, including the plugin-forwarding branch calling through the chain-aware RPC methods added in
+   step 2.
 4. The Lua and WASM host-function equivalents.
+   - ✅ Lua: `host_compare_contents`/`host_generate_content` global functions, reachable from
+     `match_contents`/`generate_content`. Done in both drivers, each of which has its own Lua
+     plugin runtime: Rust (`lua_plugin.rs`, via `mlua`) and JVM (`LuaPactPlugin.kt`/
+     `LuaPluginRpcClient.kt`, via `luajava`). Both reuse the same resolver added in step 2 -
+     `catalogue_manager::resolve_capability` (Rust) / `CatalogueManager.resolveCapability` (JVM) -
+     shared with the gRPC `PluginHost` callback path.
+   - ⬜ WASM: not yet started (blocked on [003](/implementation_guides/pact_plugins/docs/proposals/proposal_003_support_wasm_plugins) landing WASM plugin
+     support at all).
 
 This is deliberately the smallest slice that proves the mechanism end-to-end, because `is_core()` already exists as an
 unfinished seam. [006](/implementation_guides/pact_plugins/docs/proposals/proposal_006_field_level_matchers_and_generators) then adds new capability trait shapes

website/docs/implementation_guides/pact_plugins/docs/proposals/proposal_009_host_provided_core_matching_and_generation.md

@@ -53,6 +53,22 @@ generator set through the 007 mechanism, and confirming the 006 field-level shap
 context where the rule requires it — e.g. a `date` generator needing the current time, or a rule needing sibling
 values).
 
+### Sequencing
+
+1. ✅ 007's content-level mechanism (the `CoreContentMatcher`/`CoreContentGenerator` registry and the extended
+   `PluginHost` gRPC service with cycle detection and deadline propagation). Done in both drivers — Rust
+   (`core_capabilities.rs`, `call_chain.rs`, `plugin_host.rs`) and JVM (`CoreCapabilities.kt`, `CallChain.kt`,
+   `PluginHostServer.kt`) — see [007](/implementation_guides/pact_plugins/docs/proposals/proposal_007_driver_plugin_callback_model#sequencing). This unblocks registering
+   any *content-level* standard matcher/generator (a whole content type, not a single field) through the mechanism
+   today.
+2. ⬜ [006](/implementation_guides/pact_plugins/docs/proposals/proposal_006_field_level_matchers_and_generators)'s field-level operation shape. Not started. Blocks
+   registering the field-level standard rules (`type`, `regex`, `equality`, etc. applied to a single field rather
+   than a whole content type), which is most of what this proposal is actually for.
+3. ⬜ Register the standard Pact matcher/generator set as `CORE` catalogue entries with handlers implementing 007's
+   traits (content-level now possible; field-level blocked on step 2). Not started.
+4. ⬜ WASM and Lua host-function equivalents, following [007](/implementation_guides/pact_plugins/docs/proposals/proposal_007_driver_plugin_callback_model#sequencing)'s
+   step 4. Not started.
+
 ## Recommended direction
 
 - Treat standard Pact matching and generation as host capabilities registered through the [007](/implementation_guides/pact_plugins/docs/proposals/proposal_007_driver_plugin_callback_model)