demo docs fixes :

- fix issue #624
- fix issue #623
- fix issue #622
- fix issue #621

Author: Seburan

services/home/docs/demos/bidding-and-auction.md

@@ -89,8 +89,9 @@ components of the system work together to complete an auction.
 
 #### User Journey
 
-```bash
+```mermaid
 sequenceDiagram
+
     Browser->>+Advertiser: User visits a shop site and clicks on a product
     DSP -->>DSP: DSP implements payload optimization
     DSP-->>Browser: DSP calls navigator.joinAdInterestGroup(...)
@@ -110,7 +111,7 @@ sequenceDiagram
     Publisher Page-->>Browser: Top level seller runs navigator.runAdAuction(auctionConfig) on-device
 ```
 
-#TODO: add valid permalink ![User Journey](../demos/img/bidding-and-auction-flow.png)
+[Full-sized diagram](./img/bidding-and-auction-flow.png)
 
 </TabItem>
 
@@ -632,7 +633,7 @@ sspYRouter.get('/construct-component-auction.js', async (req, res) => {
 ```
 
 7. The
-   [construct-component-auction.ts](https://github.com/privacysandbox/privacy-sandbox-demos/blob/dev/services/ad-tech/src/public/js/ssp/usecase/bidding-and-auction/ssp-y/construct-component-auction.ts#L35)
+   [construct-component-auction.ts](https://github.com/privacysandbox/privacy-sandbox-demos/blob/ff68148e0987979ecdac2f0183b9ca2a1b847bcc/services/ad-tech/src/public/js/ssp/usecase/bidding-and-auction/ssp-y/construct-component-auction.ts#L35)
    file will first build the auction config.
 
 ```typescript
@@ -755,10 +756,10 @@ async #runComponentAdAuction(request: number[]) {
     The selectAd request can also be sent with a REST API call. This
     [proto file](https://github.com/privacysandbox/privacy-sandbox-demos/blob/e9b604243b99c4629b78a578844d054770f9d660/services/ad-tech/src/routes/ssp/usecase/bidding-and-auction/server/proto/sfe-client.proto#L3)
     defines the interface for interacting with the seller frontend service. The `ciphertextShaHash` uses the response from the seller front end and
-    generates a SHA-256 hash with base64 encoding. This is to ensure payload security between the seller ad service and the browser.  
-    The ciphertext is then set as the value for the `Ad-Auction-Result` header to be passed back to the browser. The `onDeviceAuctionConfig` field is
-    set to define the auction configuration for the on-device component of mixed mode. This will be passed to the browser along with the bidding and
-    auction result, but it will appear as a separate component auction in the browser.
+    generates a SHA-256 hash with base64 encoding. This is to ensure payload security between the seller ad service and the browser. The ciphertext is
+    then set as the value for the `Ad-Auction-Result` header to be passed back to the browser. The `onDeviceAuctionConfig` field is set to define the
+    auction configuration for the on-device component of mixed mode. This will be passed to the browser along with the bidding and auction result, but
+    it will appear as a separate component auction in the browser.
 
 ```typescript
    mixedModeClientSFE.selectAd(

services/home/docs/demos/instream-video-ad.md

@@ -213,7 +213,7 @@ const interestGroup = {
 
 SSPs indicate the supported ad type in `auctionConfig.auctionSignals` which is made available to the DSP's `generateBid()` method at auction time.
 Using this information, DSPs can filter for the appropriate ad types in their
-[bidding logic :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/dev/services/ad-tech/src/public/js/dsp/default/auction-bidding-logic.js#L261-264);
+[bidding logic :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/ff68148e0987979ecdac2f0183b9ca2a1b847bcc/services/ad-tech/src/public/js/dsp/usecase/default/auction-bidding-logic.js#L261-264);
 
 #### What does the interest group ad creative do?
 
@@ -232,11 +232,11 @@ includes a single
 wrapping the VAST XML.
 
 This script starts by
-[parsing :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/67d4c6368ff422ad9e952961352b5ac74ee9f500/services/ad-tech/src/public/js/video-ad-frame.js#L38-48)
+[parsing :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/ff68148e0987979ecdac2f0183b9ca2a1b847bcc/services/ad-tech/src/public/js/video-ads.js#L38)
 the SSP's VAST wrapping endpoint including in the URL. Then the scripts proceeds to
-[fetch the finalized VAST XML from this SSP endpoint :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/67d4c6368ff422ad9e952961352b5ac74ee9f500/services/ad-tech/src/public/js/video-ad-frame.js#L51-69)
+[fetch the finalized VAST XML from this SSP endpoint :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/ff68148e0987979ecdac2f0183b9ca2a1b847bcc/services/ad-tech/src/public/js/video-ads.js#L51)
 before
-[post-messaging the XML content to the top frame :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/dev/services/ad-tech/src/public/js/video-ad-frame.js#L107-115).
+[post-messaging the XML content to the top frame :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/ff68148e0987979ecdac2f0183b9ca2a1b847bcc/services/ad-tech/src/public/js/video-ads.js#L108).
 
 ```js title="Winning PA ad iframe assembles and post-messages the finalized VAST to the top frame"
 // ...

services/home/docs/demos/multi-piece-ad.md

@@ -36,8 +36,8 @@ through a template 'container' with customizable product slots.
 ### Goals
 
 In this demo, the auction setup and execution is similar to the
-[sequential setup of Protected Audience with contextual ad auction](https://privacy-sandbox-demos.dev/docs/demos/sequential-auction-setup/) demo. So,
-please check this use case implementation first if you want to learn about the Protected Audience auction setup.
+[sequential setup of Protected Audience with contextual ad auction](./sequential-auction-setup) demo. So, please check this use case implementation
+first if you want to learn about the Protected Audience auction setup.
 
 The only incremental difference in this use-case is that the advertiser can provide more than one product that the user interacted with in the same ad
 slot.

services/home/docs/demos/sequential-auction-setup.md

@@ -237,7 +237,7 @@ More specifically, the `ad-server-tag.js` injects an iframe for each ad unit whe
 Protected Audience auction to choose an ad. This iframe loads:
 [`https://privacy-sandbox-demos-ad-server.dev/ssp/run-sequential-ad-auction.html` :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/67d4c6368ff422ad9e952961352b5ac74ee9f500/services/ad-tech/src/views/ssp/run-sequential-ad-auction.ejs),
 which contains a single script:
-[`https://privacy-sandbox-demos-ad-server.dev/js/ssp/run-sequential-ad-auction.js` :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/dev/services/ad-tech/src/public/js/ssp/run-sequential-ad-auction.js).
+[`https://privacy-sandbox-demos-ad-server.dev/js/ssp/run-sequential-ad-auction.js` :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/ff68148e0987979ecdac2f0183b9ca2a1b847bcc/services/ad-tech/src/public/js/ssp/run-sequential-ad-auction.js).
 This iframe expects a post-message from `ad-server-tag.js` containing the ad unit configuration as well as the list of other sellers involved in the
 ad delivery process.
 
@@ -341,7 +341,7 @@ SellerContextualBidderRouter.get('/', async (req: Request, res: Response) => {
 
 The publisher ad servers collates the contextual bid responses from all the sellers before assembling the combined auction configuration for Protected
 Audience. In the following code snippet from
-[`run-sequential-ad-auction.js` :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/dev/services/ad-tech/src/public/js/ssp/run-sequential-ad-auction.js#L145-182),
+[`run-sequential-ad-auction.js` :arrow_upper_right:](https://github.com/privacysandbox/privacy-sandbox-demos/blob/ff68148e0987979ecdac2f0183b9ca2a1b847bcc/services/ad-tech/src/public/js/ssp/run-sequential-ad-auction.js#L154),
 the winning contextual bid is chosen purely on the bid price. Along with the contextual bid response, the additional sellers or SSPs also respond with
 their Protected Audience component auction configuration. The publisher ad server also assembles the final Protected Audience auction configuration
 which includes these component auction configurations from other sellers as well as its own component auction.