chore(docs): update migration notes relevant to v2.0.2

updates the migration notes in the docs. also fixes the background highlight color for dark mode search

Co-authored-by: Josh Crites <[email protected]>

Author: critesjosh

docs/docs/migration_notes.md

@@ -9,44 +9,6 @@ Aztec is in full-speed development. Literally every version breaks compatibility
 
 ## TBD
 
-## [Public functions]
-
-The L2 gas cost of the different AVM opcodes have been updated to reflect more realistic proving costs. Developers should review the L2 gas costs of executing public functions and reevaluate any hardcoded L2 gas limits.
-
-## [Aztec Tools]
-
-### Contract compilation now requires two steps
-
-The `aztec-nargo` command is now a direct pass-through to vanilla nargo, without any special compilation flags or postprocessing. Contract compilation for Aztec now requires two explicit steps:
-
-1. Compile your contracts with `aztec-nargo compile`
-2. Run postprocessing with the new `aztec-postprocess-contract` command
-
-The postprocessing step includes:
-
-- Transpiling functions for the Aztec VM
-- Generating verification keys for private functions
-- Caching verification keys for faster subsequent compilations
-
-Update your build scripts accordingly:
-
-```diff
-- aztec-nargo compile
-+ aztec-nargo compile
-+ aztec-postprocess-contract
-```
-
-If you're using the `aztec-up` installer, the `aztec-postprocess-contract` command will be automatically installed alongside `aztec-nargo`.
-
-## [Aztec.js] Mandatory `from`
-
-As we prepare for a bigger `Wallet` interface refactor and the upcoming `WalletSDK`, a new parameter has been added to contract interactions, which now should indicate _explicitly_ the address of the entrypoint (usually the account contract) that will be used to authenticate the request. This will be checked in runtime against the current `this.wallet.getAddress()` value, to ensure consistent behavior while the rest of the API is reworked.
-
-```diff
-- await contract.methods.my_func(arg).send().wait();
-+ await contract.methods.my_func(arg).send({ from: account1Address }).wait();
-```
-
 ## [Aztec.nr]
 
 ### Historical block renamed as anchor block
@@ -58,7 +20,7 @@ This naming change resulted in quite a few changes and if you've access private
 ```diff
 - let header = context.get_block_header();
 + let header = context.get_anchor_block_header();
-```diff
+```
 
 ### PrivateMutable: replace / initialize_or_replace behaviour change
 
@@ -92,7 +54,6 @@ This makes it easy and efficient to handle both initialization and current value
 + storage.my_var.initialize_or_replace(|opt_current: Option<Note>| opt_current.unwrap_or(0 /* initial value */) + 1);
 ```
 
-
 - The callback can be a closure (inline) or a named function.
 - Any previous assumptions that replace simply inserts a new_note directly must be updated.
 
@@ -162,6 +123,48 @@ Then update the emissions:
 + storage.balances.at(owner).insert(note).emit(&mut context, context.msg_sender(), MessageDelivery.UNCONSTRAINED_OFFCHAIN);
 ```
 
+## 2.0.2
+
+## [Public functions]
+
+The L2 gas cost of the different AVM opcodes have been updated to reflect more realistic proving costs. Developers should review the L2 gas costs of executing public functions and reevaluate any hardcoded L2 gas limits.
+
+## [Aztec Tools]
+
+### Contract compilation now requires two steps
+
+The `aztec-nargo` command is now a direct pass-through to vanilla nargo, without any special compilation flags or postprocessing. Contract compilation for Aztec now requires two explicit steps:
+
+1. Compile your contracts with `aztec-nargo compile`
+2. Run postprocessing with the new `aztec-postprocess-contract` command
+
+The postprocessing step includes:
+
+- Transpiling functions for the Aztec VM
+- Generating verification keys for private functions
+- Caching verification keys for faster subsequent compilations
+
+Update your build scripts accordingly:
+
+```diff
+- aztec-nargo compile
++ aztec-nargo compile
++ aztec-postprocess-contract
+```
+
+If you're using the `aztec-up` installer, the `aztec-postprocess-contract` command will be automatically installed alongside `aztec-nargo`.
+
+## [Aztec.js] Mandatory `from`
+
+As we prepare for a bigger `Wallet` interface refactor and the upcoming `WalletSDK`, a new parameter has been added to contract interactions, which now should indicate _explicitly_ the address of the entrypoint (usually the account contract) that will be used to authenticate the request. This will be checked in runtime against the current `this.wallet.getAddress()` value, to ensure consistent behavior while the rest of the API is reworked.
+
+```diff
+- await contract.methods.my_func(arg).send().wait();
++ await contract.methods.my_func(arg).send({ from: account1Address }).wait();
+```
+
+## [Aztec.nr]
+
 ### `emit_event_in_public_log` function renamed as `emit_event_in_public`
 
 This change was done to make the naming consistent with the private counterpart (`emit_event_in_private`).
@@ -316,7 +319,7 @@ The `private` and `public` methods are gone. Private, public and utility context
 
 The following are two tests using the older version of `TestEnvironment`:
 
-```noir
+```rust
 #[test]
 unconstrained fn initial_empty_value() {
     let mut env = TestEnvironment::new();
@@ -356,7 +359,7 @@ unconstrained fn non_admin_cannot_set_authorized() {
 
 These now look like this:
 
-```noir
+```rust
 #[test]
 unconstrained fn authorized_initially_unset() {
     let mut env = TestEnvironment::new();
@@ -1152,7 +1155,7 @@ This is a breaking change because we now require `Packable` trait implementation
 
 Example implementation of Packable trait for `U128` type from `noir::std`:
 
-```
+```rust
 use crate::traits::{Packable, ToField};
 
 let U128_PACKED_LEN: u32 = 1;

docs/src/css/custom.css

@@ -118,6 +118,14 @@
   --brand-background: #1a1400;
   --ifm-font-color-base: #f2eee1;
   background: #1a1400;
+
+  /* Dark theme Typesense/DocSearch contrast improvements */
+  --docsearch-modal-background: #1a1400;
+  --docsearch-hit-background: #a9cc1f;
+  --docsearch-highlight-color: #a9cc1f;
+  --docsearch-text-color: #f2eee1;
+  --docsearch-muted-color: #999;
+  --docsearch-searchbox-focus-background: #2a2000;
 }
 
 [data-theme="dark"] .footer {
@@ -405,4 +413,4 @@ html[data-theme="dark"] .sidebar-divider {
 
 .badge {
   border-radius: unset;
-}
+}

docs/versioned_docs/version-v2.0.2/migration_notes.md

@@ -7,7 +7,7 @@ tags: [migration, updating, sandbox]
 
 Aztec is in full-speed development. Literally every version breaks compatibility with the previous ones. This page attempts to target errors and difficulties you might encounter when upgrading, and how to resolve them.
 
-## TBD
+## 2.0.2
 
 ## [Aztec Tools]
 
@@ -56,9 +56,9 @@ The private event emission API has been significantly reworked to provide cleare
 1. `emit_event_in_private_log` has been renamed to `emit_event_in_private` and now takes a `delivery_mode` parameter instead of `constraints`
 2. `emit_event_as_offchain_message` has been removed in favor of using `emit_event_in_private` with `MessageDelivery.UNCONSTRAINED_OFFCHAIN`
 3. `PrivateLogContent` enum has been replaced with `MessageDelivery` enum with the following values:
-   - `CONSTRAINED_ONCHAIN`: For onchain delivery with cryptographic guarantees (replaces `CONSTRAINED_ENCRYPTION`)
-   - `UNCONSTRAINED_OFFCHAIN`: For offchain delivery without constraints
-   - `UNCONSTRAINED_ONCHAIN`: For onchain delivery without constraints (replaces `NO_CONSTRAINTS`)
+   - `CONSTRAINED_ONCHAIN`: For onchain delivery with cryptographic guarantees that recipients can discover and decrypt messages. Uses constrained encryption but is slower to prove. Best for critical messages that contracts need to verify.
+   - `UNCONSTRAINED_ONCHAIN`: For onchain delivery without encryption constraints. Faster proving but trusts the sender. Good when the sender is incentivized to perform encryption correctly (e.g. they are buying something and will only get it if the recipient sees the note). No guarantees that recipients will be able to find or decrypt messages.
+   - `UNCONSTRAINED_OFFCHAIN`: For offchain delivery (e.g. cloud storage) without constraints. Lowest cost since no onchain storage needed. Requires custom infrastructure for delivery. No guarantees that messages will be delivered or that recipients will ever find them.
 
 ### Contract functions can no longer be `pub` or `pub(crate)`