Bidi: Implement last redirect (#2972)

* Bidi: Implement last redirect

* Apply suggestion from @Copilot

Co-authored-by: Copilot <[email protected]>

* Apply suggestion from @Copilot

Co-authored-by: Copilot <[email protected]>

* Apply suggestion from @Copilot

Co-authored-by: Copilot <[email protected]>

* Update lib/CLAUDE.md

Co-authored-by: Copilot <[email protected]>

* Apply suggestion from @kblok

---------

Co-authored-by: Copilot <[email protected]>

Author: kblok

.gitignore

@@ -299,3 +299,4 @@ samples/PupppeterSharpAspNetFrameworkSample/PupppeterSharpAspNetFrameworkSample/
 # Visual Studio Code user config directory
 .vscode/
 tools/github-ops/.env
+lib/.claude/settings.local.json

lib/.claude/commands/implement-bidi-feature.md

@@ -0,0 +1,18 @@
+# Context
+You are a software developer integrating changes from a project written in TypeScript into a .NET project.
+We call upstream to the original typescript project.
+
+# Task
+
+You are going to implement the changes to make $ARGUMENTS pass.
+
+In order to do that you will need to:
+ * Find the entry with the `testIdPattern` $ARGUMENTS in TestExpectations.local.json and remove that entry.
+ * You are going to look for tests that might match that `testIdPattern` but looking at the test attribute.
+    - For instance if the `testIdPattern` is `Chromium-Specific *`, `[Test, PuppeteerTest("chromiumonly.spec", "Chromium-Specific Page Tests", "Page.setRequestInterception should work with intervention headers")]` will be a valid match.
+ * Once you see what fail in those tests you will need to modify the code to make the test pass. You should not edit the tests themselves.
+ * You will find the code in typescript implementing the feature at ../../puppeteer/puppeteer and you will need to port that code to .NET.
+ * You will also find BidiDriver code at ../../puppeteer/bidi-client you need to check what you need to use from there to make the tests pass.
+ * You will have to implement the code as close as possible to the original code, but adapted to .NET idioms and practices.
+ * As part of the task you will need to generate a document explaining the changes you made, and how they relate to the original PR.
+ * You need to run related tests to ensure everything is working as expected.

lib/.claude/commands/implement-upstream-change.md

@@ -0,0 +1,17 @@
+# Context
+You are a software developer integrating changes from a project written in TypeScript into a .NET project.
+We call upstream to the original typescript project.
+
+# Task
+
+You are going to check the changes on the PR $ARGUMENTS
+You will find the upstream repository at ../../puppeteer/puppeteer. Feel free to read the code there and even make git action to bring the changes you need to evaluate.
+
+Once you have all the context, you will implement the same changes in this .NET project.
+You will create a new branch named `implement-upstream-change-<PR_NUMBER>` where `<PR_NUMBER>` is the number of the PR you are implementing.
+You will have to implement the code as close as possible to the original code, but adapted to .NET idioms and practices.
+
+As part of the task you will need to generate a document explaining the changes you made, and how they relate to the original PR.
+
+You need to run related tests to ensure everything is working as expected.
+If tests are failing, you will need to fix them.