.github/workflows/test-getting-started.yml

@@ -16,23 +16,23 @@ jobs:
         with:
           node-version: '18'
       - name: Creating Your Dapp From a Template
-        run: yarn create @agoric/dapp demo
+        run: yarn create @agoric/dapp offer-up
       - name: Install dependencies
         run: |
-          cd demo
+          cd offer-up
           corepack enable
           yarn install
       - name: Start the Docker container
         run: |
-          cd demo
+          cd offer-up
           yarn start:docker
       - name: Wait for Docker container to be ready
         run: |
-          cd demo
+          cd offer-up
           yarn runWaitForBlocks
       - name: yarn start:contract
         run: |
-          cd demo
+          cd offer-up
           yarn start:contract
       - name: verify contracts started onchain
         run: |

.github/workflows/test-markdown.yml

@@ -5,11 +5,11 @@ name: Lint Markdown
 
 on:
   push:
-    branches: [$default-branch]
+    branches: [main]
   pull_request:
 
 jobs:
-  build:
+  lint-markdown:
     runs-on: ubuntu-latest
     strategy:
       matrix:

.prettierrc.json

@@ -2,7 +2,6 @@
     "printWidth": 80,
     "tabWidth": 2,
     "useTabs": false,
-    "semi": false,
     "singleQuote": true,
     "proseWrap": "preserve",
     "trailingComma": "none",

CONTRIBUTING.md

@@ -107,7 +107,7 @@ module.exports = {
   themeConfig: {
     sidebar: 'auto'
   }
-}
+};
 ```
 
 Or, add a config entry, either as part of a group or as an individual page.
@@ -133,7 +133,7 @@ module.exports = {
       }
     ]
   }
-}
+};
 ```
 
 ## Writing Links
@@ -564,8 +564,8 @@ export default ({ router }) => {
       path: '/getting-started/agoric-cli-guide.html',
       redirect: '/guides/agoric-cli/'
     }
-  ])
-}
+  ]);
+};
 ```
 
 The general format should be self-explanatory. However, there are two things you need to know that aren't apparent

main/.vitepress/config.mjs

@@ -120,6 +120,35 @@ export default defineConfig({
     // Trailing slash implies it is looking for a .md file
     sidebar: {
       '/': [
+        {
+          text: 'Orchestrate',
+          link: '/guides/orchestration/',
+          collapsed: true,
+          items: [
+            {
+              text: 'Key Concepts and APIs',
+              link: '/guides/orchestration/getting-started/key-concepts',
+            },
+            {
+              text: 'Contract Walkthroughs',
+              link: '/guides/orchestration/getting-started/contract-walkthroughs',
+              items: [
+                {
+                  text: 'Cross-Chain Swap Example',
+                  link: '/guides/orchestration/getting-started/contract-walkthrough/cross-chain-swap',
+                },
+                {
+                  text: 'Cross-Chain Unbond Example',
+                  link: '/guides/orchestration/getting-started/contract-walkthrough/cross-chain-unbond',
+                },
+                {
+                  text: 'Orchestration Basics',
+                  link: '/guides/orchestration/getting-started/contract-walkthrough/orchestration-basics',
+                }
+              ]
+            },
+          ]
+        },
         {
           text: 'Build',
           collapsed: true,
@@ -426,13 +455,9 @@ export default defineConfig({
               collapsed: true,
               items: [
                 {
-                  text: 'Key Concepts',
+                  text: 'Key Concepts and APIs',
                   link: '/guides/orchestration/getting-started/key-concepts',
                 },
-                {
-                  text: 'API',
-                  link: '/guides/orchestration/getting-started/api',
-                },
                 {
                   text: 'Contract Walkthroughs',
                   link: '/guides/orchestration/getting-started/contract-walkthroughs',

main/.vitepress/themeConfig/nav.js

@@ -5,6 +5,41 @@
 // Trailing slash implies it is looking for a .md file
 
 export const nav = [
+  {
+    text: 'Orchestrate',
+    collapsed: true,
+    items: [
+      {
+        text: 'What is Orchestration?',
+        link: '/guides/orchestration/',
+      },
+      {
+        text: 'Key Concepts',
+        link: '/guides/orchestration/getting-started/key-concepts',
+      },
+      {
+        text: 'API',
+        link: '/guides/orchestration/getting-started/api',
+      },
+      {
+        text: 'Contract Walkthroughs',
+        items: [
+          {
+            text: 'Cross-Chain Swap Example',
+            link: '/guides/orchestration/getting-started/contract-walkthrough/cross-chain-swap',
+          },
+          {
+            text: 'Cross-Chain Unbond Example',
+            link: '/guides/orchestration/getting-started/contract-walkthrough/cross-chain-unbond',
+          },
+          {
+            text: 'Orchestration Basics',
+            link: '/guides/orchestration/getting-started/contract-walkthrough/orchestration-basics',
+          }
+        ]
+      },
+    ]
+  },
   {
     text: 'Build',
     items: [
@@ -82,12 +117,6 @@ export const nav = [
         collapsed: true,
         items: [],
       },
-      {
-        text: 'Orchestration',
-        link: '/guides/orchestration/',
-        collapsed: true,
-        items: [],
-      },
       {
         text: 'Zoe Smart Contract Framework',
         link: '/guides/zoe/',

main/e2e-testing.md

@@ -40,16 +40,16 @@ Before you start writing your E2E tests, you'll need to create a configuration f
 Inside `synpress.config.js`, you'll set the `baseUrl` property within the e2e configuration. This tells Cypress where to find your DApp during testing. Here's an example configuration:
 
 ```js
-const baseConfig = require('@agoric/synpress/synpress.config')
-const { defineConfig } = require('cypress')
+const baseConfig = require('@agoric/synpress/synpress.config');
+const { defineConfig } = require('cypress');
 
 module.exports = defineConfig({
   ...baseConfig,
   e2e: {
     ...baseConfig.e2e,
     baseUrl: 'http://localhost:5173'
   }
-})
+});
 ```
 
 In this example, `baseUrl` is set to `http://localhost:5173`. Make sure to replace this with the actual URL where your DApp is running.
@@ -69,7 +69,7 @@ Navigate to your project's `tests/e2e` directory and create a new file named `su
 After creating your `support.js` file, make sure to include the following import statement:
 
 ```js
-import '@agoric/synpress/support/index'
+import '@agoric/synpress/support/index';
 ```
 
 This import is essential because it brings in the necessary functionalities from `@agoric/synpress` to interact with the Keplr wallet within your e2e tests. Without it, your tests won't be able to leverage the features provided by `@agoric/synpress` for Keplr integration.
@@ -86,8 +86,8 @@ You use `describe` blocks to group related tests together, and `it` blocks to de
 describe('User Login', () => {
   it('should login with valid credentials', () => {
     // Test steps for login functionality
-  })
-})
+  });
+});
 ```
 
 ### Test 1: Setting Up Keplr Wallet
@@ -96,9 +96,9 @@ describe('User Login', () => {
 it('should setup a Keplr wallet', () => {
   cy.setupWallet({
     secretWords: 'KEPLR_MNEMONIC'
-  })
-  cy.visit('/')
-})
+  });
+  cy.visit('/');
+});
 ```
 
 This test case simulates setting up a Keplr wallet for your tests, using the `cy.setupWallet` method. Make sure to replace `KEPLR_MNEMONIC` with a 24-word mnemonic phrase. The `setupWallet` method creates a wallet based on the provided mnemonic phrase, which can then be used throughout your test suite.
@@ -109,9 +109,9 @@ After setting up the wallet, we visit the root path (`/`) of the DApp using `cy.
 
 ```js
 it('should accept connection with wallet', () => {
-  cy.contains('Connect Wallet').click()
-  cy.acceptAccess()
-})
+  cy.contains('Connect Wallet').click();
+  cy.acceptAccess();
+});
 ```
 
 This test simulates a user connecting their Keplr wallet to your DApp. `cy.contains('Connect Wallet')` searches for an element containing the text `Connect Wallet` on the webpage and triggers a click event. `cy.acceptAccess` simulates accepting Keplr wallet access for your DApp.
@@ -120,9 +120,9 @@ This test simulates a user connecting their Keplr wallet to your DApp. `cy.conta
 
 ```js
 it('should confirm make an offer transaction', () => {
-  cy.contains('Make an Offer').click()
-  cy.confirmTransaction()
-})
+  cy.contains('Make an Offer').click();
+  cy.confirmTransaction();
+});
 ```
 
 This test simulates transaction Signing on your DApp. `cy.contains('Make an Offer')` searches for an element containing the text `Make an Offer` and triggers a click event. `cy.confirmTransaction` simulates confirming a transaction.

main/glossary/index.md

@@ -141,10 +141,10 @@ and the [ERTP API's Brand section](/reference/ertp-api/brand).
 Before a contract can be installed on Zoe, its source code must be bundled. This is done by:
 
 ```js
-import bundleSource from '@endo/bundle-source'
+import bundleSource from '@endo/bundle-source';
 const atomicSwapBundle = await bundleSource(
   require.resolve('@agoric/zoe/src/contracts/atomicSwap')
-)
+);
 ```
 
 The installation operation returns an `installation`, which is an object with a single
@@ -153,7 +153,7 @@ In most cases, the bundle contains a base64-encoded zip file that you can
 extract for review.
 
 ```js
-const { endoZipBase64 } = await E(installation).getBundle()
+const { endoZipBase64 } = await E(installation).getBundle();
 ```
 
 ```sh
@@ -296,10 +296,10 @@ A _facet_ is an object that exposes an API or particular view of some larger ent
 You can make any number of facets of an entity. In JavaScript, you often make a facet that forwards method calls:
 
 ```js
-import { Far } from '@endo/far'
+import { Far } from '@endo/far';
 const facet = Far('FacetName', {
   myMethod: (...args) => oldObject.method(...args)
-})
+});
 ```
 
 Two Agoric uses are:
@@ -495,6 +495,20 @@ vat-orchestration. This [vat](/glossary/#vat) manages [Inter-Chain Account (ICA)
 chains, ensuring proper transaction authorization.
 For more information, see the [Orchestration API](/guides/orchestration/).
 
+## Orthogonal Persistence
+
+Orthogonal Persistence refers to a persistence model in which it appears to the programmer as if the program's memory is always there forever.
+The system automatically keeps the entire memory state in such a way that computation can always resume after events like crashes or restarts.
+This means the programmer doesn't need to explicitly save or restore any data, making for an easy and convenient programming model.
+
+Orthogonal persistence is contrasted with:
+
+- Manual Persistence: Where all in-memory state is volatile, and anything you want saved you have to explicitly save yourself, such as by writing
+  to a file or database. All acts of recording and recovering state are deliberate actions performed by the code.
+- Automatic Persistence: Where certain data is designated to be kept, either declaratively or through procedural interfaces.
+  Updates to this data are automatically saved and available upon resuming execution, but the programmer may still need to manually
+  reestablish in-memory invariants when the program starts or restarts.
+
 ## Passable
 
 A _passable_ is something that can be sent to and from remote objects.
@@ -550,7 +564,7 @@ const myProposal = harden({
   give: { Asset: AmountMath.make(quatloosBrand, 4n) },
   want: { Price: AmountMath.make(moolaBrand, 15n) },
   exit: { onDemand: null }
-})
+});
 ```
 
 `give` and `want` each associate [Keywords](#keyword) defined by the contract with corresponding [Amounts](#amount) describing respectively what will be given and what is being requested in exchange.

main/guides/coreeval/permissions.md

@@ -25,9 +25,9 @@ export const permit = harden({
   instance: { produce: { [contractName]: true } },
   issuer: { consume: { IST: true }, produce: { Ticket: true } },
   brand: { consume: { IST: true }, produce: { Ticket: true } }
-})
+});
 
-export const main = startSellConcertTicketsContract
+export const main = startSellConcertTicketsContract;
 ```
 
 ## Selected BootstrapPowers
@@ -49,7 +49,7 @@ In the top level promise space, we have:
   **Warning: this includes access to over-write previously allocated storage nodes.**
 
 - **chainTimerService**: for getting the current timer and setting timer wake-ups; for example, at the conclusion of a governance vote.
-  See [Timer Service API](../../reference/repl/timerServices).
+  See [Timer Service API](/reference/repl/timerServices).
   **Note: this includes access to schedule infinitely repeating events.**
 
 - **namesByAddress**: for [looking up objects published under an address](../integration/name-services#namesbyaddress-namesbyaddressadmin-and-depositfacet-per-account-namespace); in particular,
@@ -60,6 +60,6 @@ In the top level promise space, we have:
 
 - **priceAuthority**: access to get price quotes and triggers; see [Price Authority Guide](../zoe/price-authority).
 
-- **priceAuthorityAdmin**: access to add and replace sources of price quotes using [E(priceAuthorityAdmin).registerPriceAuthority()](../../reference/zoe-api/price-authority-admin#e-priceauthorityregistryadmin-registerpriceauthority-priceauthority-brandin-brandout-force)
+- **priceAuthorityAdmin**: access to add and replace sources of price quotes using [E(priceAuthorityAdmin).registerPriceAuthority()](/reference/zoe-api/price-authority-admin#e-priceauthorityregistryadmin-registerpriceauthority-priceauthority-brandin-brandout-force)
 
-- **zoe**: the [Zoe service](../../reference/zoe-api//zoe)
+- **zoe**: the [Zoe service](/reference/zoe-api/zoe)