@@ -28,6 +28,9 @@ function getSignInCredentials(): {username: string; password: string} {
  * - IS: WSO2 IS authentication endpoint
  */
 export async function performSignIn(page: Page): Promise<void> {
+  // Fail fast on an invalid IDP_TARGET instead of silently running the IS flow.
+  getIdpTarget();
+
   const credentials = getSignInCredentials();
 
   await performIsSignIn(page, credentials);
 
@@ -2,15 +2,18 @@
 
 Shared lint and formatting configuration used by every package in this workspace.
 
-Both packages are vendored copies of
-[`brionmario/wso2-ui-configs`](https://github.com/brionmario/wso2-ui-configs) at commit
-`d3041825a4f8f235c8f9fa36b55cf29d54e791c8` (Apache-2.0, see `LICENSE`):
+Both packages are vendored copies of [`brionmario/wso2-ui-configs`](https://github.com/brionmario/wso2-ui-configs) at
+commit `d3041825a4f8f235c8f9fa36b55cf29d54e791c8` (Apache-2.0, see `LICENSE`):
 
 - `eslint-plugin/` — `@wso2/eslint-plugin` (`packages/eslint-plugin` upstream)
 - `prettier-config/` — `@wso2/prettier-config` (`packages/prettier-config` upstream)
 
-They used to be consumed as git dependencies with a `path:` subdirectory. pnpm resolves GitHub-hosted git
-dependencies to a tarball of the whole repository and drops the `path:` fragment, so a clean install (CI, or a
-fresh store) ended up with the repository root instead of the package and ESLint could not find the plugin.
-Consuming them as workspace packages makes installs deterministic. To update, copy the upstream package
-contents over these directories and bump the commit above.
+They used to be consumed as git dependencies with a `path:` subdirectory. pnpm resolves GitHub-hosted git dependencies
+to a tarball of the whole repository and drops the `path:` fragment, so a clean install (CI, or a fresh store) ended up
+with the repository root instead of the package and ESLint could not find the plugin. Consuming them as workspace
+packages makes installs deterministic. To update, copy the upstream package contents over these directories and bump the
+commit above.
+
+Local deviations from upstream, to re-apply after an update: `package.json` is trimmed and marked `private`, the READMEs
+describe `workspace:*` usage instead of registry installation, and the README/TROUBLESHOOTING Markdown was fixed to pass
+markdownlint. Library code under `lib/` and `index.js` is unchanged.
@@ -4,45 +4,20 @@ ESLint plugin containing configurations & custom rules used in WSO2 code bases.
 
 ## Installation
 
-You'll first need to install [ESLint](https://eslint.org/):
+This is a private workspace package (`"private": true`) vendored from
+[`brionmario/wso2-ui-configs`](https://github.com/brionmario/wso2-ui-configs); it is not published to a registry.
+Packages in this monorepo consume it with a `workspace:*` dependency:
 
-### With npm
-
-```sh
-npm i eslint --save-dev
-```
-
-### With pnpm
-
-```sh
-pnpm add --save-dev eslint
-```
-
-### With Yarn
-
-```sh
-yard add --dev eslint
-```
-
-Next, install `@wso2/eslint-plugin`:
-
-### With npm
-
-```sh
-npm i @wso2/eslint-plugin --save-dev
-```
-
-### With pnpm
-
-```sh
-pnpm add --save-dev @wso2/eslint-plugin
+```json
+{
+  "devDependencies": {
+    "@wso2/eslint-plugin": "workspace:*",
+    "eslint": "8.57.0"
+  }
+}
 ```
 
-### With Yarn
-
-```sh
-yard add --dev @wso2/eslint-plugin
-```
+See [`../README.md`](../README.md) for provenance and how to update the vendored copy.
 
 ## Usage
 
@@ -88,21 +63,15 @@ If you're working on a React project, do the following extension in your `eslint
 
 ```json
 {
-  "extends": [
-    "plugin:@wso2/javascript"
-    "plugin:@wso2/react",
-  ]
+  "extends": ["plugin:@wso2/javascript", "plugin:@wso2/react"]
 }
 ```
 
 #### React TypeScript
 
 ```json
 {
-  "extends": [
-    "plugin:@wso2/typescript"
-    "plugin:@wso2/react",
-  ]
+  "extends": ["plugin:@wso2/typescript", "plugin:@wso2/react"]
 }
 ```
 
 
@@ -10,11 +10,11 @@ If you're using the ESLint Plugin inside a Create React App project, you might e
 [eslint] Plugin "@typescript-eslint" was conflicted between ".eslintrc.cjs » plugin:@wso2/react » plugin:@wso2/typescript#overrides[0]" and ".eslintrc.cjs » plugin:@wso2/react » plugin:@wso2/typescript » eslint-config-airbnb-typescript/base » /<PATH>/node_modules/.pnpm/eslint-config-airbnb-typescript@17.0.0_mnxwss6wgpp5zz53fmtbuvhzim/node_modules/eslint-config-airbnb-typescript/lib/shared.js".
 ```
 
-#### Reason
+### Reason
 
 A possible reason for the above would be that Create React app has it's own eslint configuration([eslint-config-react-ap](https://github.com/facebook/create-react-app/tree/main/packages/eslint-config-react-app)). This package has it's own eslint-plugins declared as dependencies and these can cause conflicts. Even if you remove the extension in the eslint config, there's no way to remove this dependency without ejecting.
 
-#### Workaround
+### Workaround
 
 You can disable the inbuilt eslint plugin using the following config.
 
 
@@ -4,45 +4,20 @@ Shareable Prettier configurations used in WSO2 code bases.
 
 ## Installation
 
-You'll first need to install [Prettier](https://prettier.io/):
-
-### With npm
-
-```sh
-npm i prettier --save-dev
-```
-
-### With pnpm
-
-```sh
-pnpm add --save-dev prettier
+This is a private workspace package (`"private": true`) vendored from
+[`brionmario/wso2-ui-configs`](https://github.com/brionmario/wso2-ui-configs); it is not published to a registry.
+Packages in this monorepo consume it with a `workspace:*` dependency:
+
+```json
+{
+  "devDependencies": {
+    "@wso2/prettier-config": "workspace:*",
+    "prettier": "2.6.2"
+  }
+}
 ```
 
-### With Yarn
-
-```sh
-yard add --dev prettier
-```
-
-Next, install `@wso2/prettier-config`:
-
-### With npm
-
-```sh
-npm i @wso2/prettier-config --save-dev
-```
-
-### With pnpm
-
-```sh
-pnpm add --save-dev @wso2/prettier-config
-```
-
-### With Yarn
-
-```sh
-yard add --dev @wso2/prettier-config
-```
+See [`../README.md`](../README.md) for provenance and how to update the vendored copy.
 
 ## Usage