CRE: warn about account key permanent bond

src/content/cre/llms-full-go.txt

@@ -7457,14 +7457,14 @@ Key linking is the process of connecting a blockchain wallet address to your CRE
 
 **Important constraints:**
 
-- **One organization per address**: Each wallet address can only be linked to one CRE organization at a time. If you need to use the same address with a different organization, you must first [unlink it](#unlinking-a-key) from the current organization.
+- **Permanent organization bond**: Once a wallet address is linked to an organization, it is permanently bonded to that organization—even if unlinked. An unlinked address can only ever be relinked to the same organization, never to a different organization. Choose your wallet carefully before linking.
 - **Per-organization key limit**: The number of web3 keys your organization can link is subject to your plan quota. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit. To request an increase, [contact us](/cre/support-feedback).
 
 However, an organization can have multiple wallet addresses linked to it, allowing team members to use their own addresses or enabling separation between development, staging, and production environments.
 
 
-<Aside type="note" title="Already linked to another organization?">
-  If you try to link an address that's already registered with another organization, the CLI will display an error. To use this address with your current organization, you must first unlink it from the other organization using cre account unlink-key (note: this will delete all workflows registered under that address in the other organization).
+<Aside type="caution" title="Permanent organization bond">
+  Once an address is linked to an organization, it is permanently bonded to that organization. Even if unlinked, the address can only ever be relinked to the same organization—never to a different organization. Make sure you're linking the correct wallet to the correct organization before confirming.
 </Aside>
 
 ## Prerequisites
@@ -7475,7 +7475,7 @@ Before linking a key, ensure you have:
 - **A CRE project directory**: You must run the command from a project directory that contains a `project.yaml` file
 - **Private key in `.env`**: Set `CRE_ETH_PRIVATE_KEY=<your_64_character_hex_key>` (without `0x` prefix) in your `.env` file
 - **Funded wallet**: Your wallet must have ETH on Ethereum Mainnet to pay for gas fees (the Workflow Registry contract is deployed on Ethereum Mainnet)
-- **Unlinked address**: The wallet address must not already be linked to another CRE organization. Each address can only be associated with one organization at a time.
+- **Unlinked address**: The wallet address must not be currently linked to any CRE organization. Once linked, an address is permanently bonded to that organization.
 
 
 <Aside type="caution" title="Never commit your .env file">
@@ -7484,6 +7484,11 @@ Before linking a key, ensure you have:
 
 ## Linking your first key
 
+
+<Aside type="caution" title="This is a permanent decision">
+  Linking a wallet address to your organization is permanent. Once linked, this address will be permanently bonded to your organization. Even if unlinked in the future, it can only ever be relinked to this organization—never to a different organization. Choose your wallet carefully and ensure you're linking it to the correct organization before confirming.
+</Aside>
+
 The easiest way to link a key is to let the deployment process handle it automatically. When you first try to [deploy a workflow](/cre/guides/operations/deploying-workflows) with `deployment-registry: "onchain:ethereum-mainnet"`, the CLI will detect that your address isn't linked and prompt you to link it.
 
 ### Automatic linking during deployment
@@ -7615,7 +7620,7 @@ Linked Owners:
 
 ## Linking multiple addresses
 
-Your organization can link more than one wallet address, subject to your plan's key limit. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit, or [contact us](/cre/support-feedback) to request an increase. Each individual address can only be linked to one organization at a time.
+Your organization can link more than one wallet address, subject to your plan's key limit. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit, or [contact us](/cre/support-feedback) to request an increase. Remember that each address becomes permanently bonded to your organization upon linking.
 
 This is useful for:
 
@@ -7633,11 +7638,15 @@ To link another address:
 
 If you need to remove a linked address from your organization, you can use the `cre account unlink-key` command. This is useful when:
 
-- Rotating addresses for security reasons
 - Removing addresses that are no longer in use
 - Cleaning up test or development addresses
 
 
+<Aside type="note" title="Unlinking does not break the permanent bond">
+  When you unlink an address, all workflows registered under that address are deleted. However, the address remains permanently bonded to your organization. If you relink it in the future, it can only be linked to this organization, not to any other organization.
+</Aside>
+
+
 <Aside type="caution" title="Destructive operation">
   **Unlinking a key will permanently delete all workflows registered under that address.** This action cannot be undone. Make sure you want to permanently remove all associated workflows before proceeding.
 </Aside>

src/content/cre/llms-full-ts.txt

@@ -7219,14 +7219,14 @@ Key linking is the process of connecting a blockchain wallet address to your CRE
 
 **Important constraints:**
 
-- **One organization per address**: Each wallet address can only be linked to one CRE organization at a time. If you need to use the same address with a different organization, you must first [unlink it](#unlinking-a-key) from the current organization.
+- **Permanent organization bond**: Once a wallet address is linked to an organization, it is permanently bonded to that organization—even if unlinked. An unlinked address can only ever be relinked to the same organization, never to a different organization. Choose your wallet carefully before linking.
 - **Per-organization key limit**: The number of web3 keys your organization can link is subject to your plan quota. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit. To request an increase, [contact us](/cre/support-feedback).
 
 However, an organization can have multiple wallet addresses linked to it, allowing team members to use their own addresses or enabling separation between development, staging, and production environments.
 
 
-<Aside type="note" title="Already linked to another organization?">
-  If you try to link an address that's already registered with another organization, the CLI will display an error. To use this address with your current organization, you must first unlink it from the other organization using cre account unlink-key (note: this will delete all workflows registered under that address in the other organization).
+<Aside type="caution" title="Permanent organization bond">
+  Once an address is linked to an organization, it is permanently bonded to that organization. Even if unlinked, the address can only ever be relinked to the same organization—never to a different organization. Make sure you're linking the correct wallet to the correct organization before confirming.
 </Aside>
 
 ## Prerequisites
@@ -7237,7 +7237,7 @@ Before linking a key, ensure you have:
 - **A CRE project directory**: You must run the command from a project directory that contains a `project.yaml` file
 - **Private key in `.env`**: Set `CRE_ETH_PRIVATE_KEY=<your_64_character_hex_key>` (without `0x` prefix) in your `.env` file
 - **Funded wallet**: Your wallet must have ETH on Ethereum Mainnet to pay for gas fees (the Workflow Registry contract is deployed on Ethereum Mainnet)
-- **Unlinked address**: The wallet address must not already be linked to another CRE organization. Each address can only be associated with one organization at a time.
+- **Unlinked address**: The wallet address must not be currently linked to any CRE organization. Once linked, an address is permanently bonded to that organization.
 
 
 <Aside type="caution" title="Never commit your .env file">
@@ -7246,6 +7246,11 @@ Before linking a key, ensure you have:
 
 ## Linking your first key
 
+
+<Aside type="caution" title="This is a permanent decision">
+  Linking a wallet address to your organization is permanent. Once linked, this address will be permanently bonded to your organization. Even if unlinked in the future, it can only ever be relinked to this organization—never to a different organization. Choose your wallet carefully and ensure you're linking it to the correct organization before confirming.
+</Aside>
+
 The easiest way to link a key is to let the deployment process handle it automatically. When you first try to [deploy a workflow](/cre/guides/operations/deploying-workflows) with `deployment-registry: "onchain:ethereum-mainnet"`, the CLI will detect that your address isn't linked and prompt you to link it.
 
 ### Automatic linking during deployment
@@ -7377,7 +7382,7 @@ Linked Owners:
 
 ## Linking multiple addresses
 
-Your organization can link more than one wallet address, subject to your plan's key limit. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit, or [contact us](/cre/support-feedback) to request an increase. Each individual address can only be linked to one organization at a time.
+Your organization can link more than one wallet address, subject to your plan's key limit. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit, or [contact us](/cre/support-feedback) to request an increase. Remember that each address becomes permanently bonded to your organization upon linking.
 
 This is useful for:
 
@@ -7395,11 +7400,15 @@ To link another address:
 
 If you need to remove a linked address from your organization, you can use the `cre account unlink-key` command. This is useful when:
 
-- Rotating addresses for security reasons
 - Removing addresses that are no longer in use
 - Cleaning up test or development addresses
 
 
+<Aside type="note" title="Unlinking does not break the permanent bond">
+  When you unlink an address, all workflows registered under that address are deleted. However, the address remains permanently bonded to your organization. If you relink it in the future, it can only be linked to this organization, not to any other organization.
+</Aside>
+
+
 <Aside type="caution" title="Destructive operation">
   **Unlinking a key will permanently delete all workflows registered under that address.** This action cannot be undone. Make sure you want to permanently remove all associated workflows before proceeding.
 </Aside>

src/content/cre/organization/linking-keys.mdx

@@ -27,14 +27,14 @@ Key linking is the process of connecting a blockchain wallet address to your CRE
 
 **Important constraints:**
 
-- **One organization per address**: Each wallet address can only be linked to one CRE organization at a time. If you need to use the same address with a different organization, you must first [unlink it](#unlinking-a-key) from the current organization.
+- **Permanent organization bond**: Once a wallet address is linked to an organization, it is permanently bonded to that organization—even if unlinked. An unlinked address can only ever be relinked to the same organization, never to a different organization. Choose your wallet carefully before linking.
 - **Per-organization key limit**: The number of web3 keys your organization can link is subject to your plan quota. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit. To request an increase, [contact us](/cre/support-feedback).
 
 However, an organization can have multiple wallet addresses linked to it, allowing team members to use their own addresses or enabling separation between development, staging, and production environments.
 
 {/* prettier-ignore */}
-<Aside type="note" title="Already linked to another organization?">
-  If you try to link an address that's already registered with another organization, the CLI will display an error. To use this address with your current organization, you must first unlink it from the other organization using <CopyText text="cre account unlink-key" code /> (note: this will delete all workflows registered under that address in the other organization).
+<Aside type="caution" title="Permanent organization bond">
+  Once an address is linked to an organization, it is permanently bonded to that organization. Even if unlinked, the address can only ever be relinked to the same organization—never to a different organization. Make sure you're linking the correct wallet to the correct organization before confirming.
 </Aside>
 
 ## Prerequisites
@@ -45,7 +45,7 @@ Before linking a key, ensure you have:
 - **A CRE project directory**: You must run the command from a project directory that contains a `project.yaml` file
 - **Private key in `.env`**: Set `CRE_ETH_PRIVATE_KEY=<your_64_character_hex_key>` (without `0x` prefix) in your `.env` file
 - **Funded wallet**: Your wallet must have ETH on Ethereum Mainnet to pay for gas fees (the Workflow Registry contract is deployed on Ethereum Mainnet)
-- **Unlinked address**: The wallet address must not already be linked to another CRE organization. Each address can only be associated with one organization at a time.
+- **Unlinked address**: The wallet address must not be currently linked to any CRE organization. Once linked, an address is permanently bonded to that organization.
 
 {/* prettier-ignore */}
 <Aside type="caution" title="Never commit your .env file">
@@ -54,6 +54,11 @@ Before linking a key, ensure you have:
 
 ## Linking your first key
 
+{/* prettier-ignore */}
+<Aside type="caution" title="This is a permanent decision">
+  Linking a wallet address to your organization is permanent. Once linked, this address will be permanently bonded to your organization. Even if unlinked in the future, it can only ever be relinked to this organization—never to a different organization. Choose your wallet carefully and ensure you're linking it to the correct organization before confirming.
+</Aside>
+
 The easiest way to link a key is to let the deployment process handle it automatically. When you first try to [deploy a workflow](/cre/guides/operations/deploying-workflows) with `deployment-registry: "onchain:ethereum-mainnet"`, the CLI will detect that your address isn't linked and prompt you to link it.
 
 ### Automatic linking during deployment
@@ -183,7 +188,7 @@ Linked Owners:
 
 ## Linking multiple addresses
 
-Your organization can link more than one wallet address, subject to your plan's key limit. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit, or [contact us](/cre/support-feedback) to request an increase. Each individual address can only be linked to one organization at a time.
+Your organization can link more than one wallet address, subject to your plan's key limit. See [Service Quotas](/cre/service-quotas#registry-quotas) for the current limit, or [contact us](/cre/support-feedback) to request an increase. Remember that each address becomes permanently bonded to your organization upon linking.
 
 This is useful for:
 
@@ -201,10 +206,14 @@ To link another address:
 
 If you need to remove a linked address from your organization, you can use the `cre account unlink-key` command. This is useful when:
 
-- Rotating addresses for security reasons
 - Removing addresses that are no longer in use
 - Cleaning up test or development addresses
 
+{/* prettier-ignore */}
+<Aside type="note" title="Unlinking does not break the permanent bond">
+  When you unlink an address, all workflows registered under that address are deleted. However, the address remains permanently bonded to your organization. If you relink it in the future, it can only be linked to this organization, not to any other organization.
+</Aside>
+
 {/* prettier-ignore */}
 <Aside type="caution" title="Destructive operation">
   **Unlinking a key will permanently delete all workflows registered under that address.** This action cannot be undone. Make sure you want to permanently remove all associated workflows before proceeding.