docs(testnet): add support channel guide and testnet changelog

testnet/docs/changelog.md

@@ -0,0 +1,95 @@
+# Testnet Changelog
+
+This log lists changes that are visible on the **Bridgelet testnet
+deployment**: new contract IDs, redeployments, changed function signatures,
+new error codes, and testnet resets. If you integrate against testnet, this
+is the only file you need to watch.
+
+It is separate from any project-wide changelog. It does not record source
+changes that haven't been deployed to testnet.
+
+Current IDs and endpoints are listed in [network-config.md](network-config.md).
+
+## How to update this file
+
+Add an entry at the top every time `scripts/deploy-testnet.sh` is run
+against testnet, every time a contract is upgraded in place, and every time
+an SDF testnet reset takes the deployment down. Each entry should include:
+
+- **Date** (UTC, `YYYY-MM-DD`) and the git commit that was deployed
+- **Contract IDs.** List new IDs, or write "unchanged".
+- **Breaking changes.** Anything that makes existing integrator code fail,
+  such as changed signatures, removed functions or new required arguments.
+- **Other changes.** New functions, new error codes, behavior fixes.
+- **Action required.** What integrators need to do, or "none".
+
+Also update `network-config.md` and `deployment-artifacts/contract-ids.txt`
+in the same PR.
+
+Entry template:
+
+```markdown
+## YYYY-MM-DD — <short title>
+
+Deployed commit: `<sha>`
+
+**Contract IDs:** unchanged | new (see below)
+**Breaking changes:** none | …
+**Other changes:** …
+**Action required:** none | …
+```
+
+---
+
+## Unreleased: not yet on testnet
+
+These changes are on `main` but **not** in the deployed testnet contracts.
+When they ship, they will move into a dated entry.
+
+**Breaking changes (EphemeralAccount):**
+- `initialize` gains an `authorized_signer: BytesN<32>` argument, between
+  `authorized_controller` and `admin`, for a total of six arguments. Existing
+  five-argument calls will fail after redeployment.
+- `initialize` enforces a network-passphrase check. On `main` the expected
+  value is currently the Standalone passphrase, which would reject testnet
+  calls with `Error(Contract, #1007)`. This must be set to the Testnet
+  passphrase before the next testnet deploy.
+
+**Other changes (EphemeralAccount):**
+- New read-only function `is_initialized() -> bool`.
+- Error codes are namespaced per contract: EphemeralAccount uses
+  1000–1999, SweepController 2000–2999, and ReserveContract 3000–3999.
+
+**Action required when this ships:** update your `initialize` calls to pass
+`authorized_signer`, and pick up any new contract IDs from
+`network-config.md`.
+
+---
+
+## 2026-07-12: Initial testnet deployment
+
+Deployed commit: `741aec2`
+
+**Contract IDs:**
+
+| Contract | Contract ID |
+|---|---|
+| EphemeralAccount | `CB7Z22TXR6ZKG7MDXIGJL6QVQQ3L3DQOFR6JV325NZK4CTYWFPVZBBP3` |
+| SweepController | `CBEU4X5MNGOECBSTNEUFMBALH2YI5YV4UIH7YXRNOLR2DNLZQD4Z5KWE` |
+| ReserveContract | `CACYMICFLHSPKVMCK336IEGCWAQB4XBC7P7HTJSQY3R7Y2YASE4AX3MS` |
+| AccountFactory | `CARBMZY4466SWP3RTN3DR2F4JYNR5UCXD2ICFISV2YI4TS3AAZV2TQ24` |
+
+EphemeralAccount WASM hash: `5e667ea0687341bdccc81538492143b573777dd04b2450cdeb89b02cee62c58e`
+
+**Interface as deployed:**
+- `EphemeralAccount::initialize(creator, expiry_ledger, recovery_address, authorized_controller, admin)`
+- `EphemeralAccount::record_payment(amount: i128, asset: Address)`
+- `SweepController::initialize(creator, authorized_signer: BytesN<32>, authorized_destination: Option<Address>)`
+- `SweepController::execute_sweep(ephemeral_account, destination, auth_signature: BytesN<64>)`
+
+**Notes:**
+- The shared EphemeralAccount instance is already initialized, and its
+  expiry ledger has passed. To test, deploy your own instance from the WASM
+  hash; see [getting-started.md](getting-started.md).
+
+**Action required:** none (first release).

testnet/docs/support.md

@@ -0,0 +1,77 @@
+# Testnet Support
+
+Use this page if you are integrating against the **Bridgelet testnet
+deployment** and something doesn't behave as expected. For example, an
+ephemeral account won't sweep, a contract ID no longer resolves, or a call
+that used to work now fails.
+
+## Is it a testnet problem?
+
+Before you file, rule out the common causes:
+
+1. **Check your network settings.** Compare your passphrase, RPC URL and
+   contract IDs against [network-config.md](network-config.md). A wrong
+   passphrase is the most common cause of `Unauthorized` errors.
+2. **Check [changelog.md](changelog.md).** The contracts may have been
+   redeployed with new IDs or new behavior since you last integrated.
+3. **Check whether testnet was reset.** The SDF resets testnet
+   periodically, and a reset wipes every account and contract. If none of
+   the IDs in `network-config.md` resolve, that is almost certainly why.
+4. **Look up the error code.** The troubleshooting table in
+   [getting-started.md](getting-started.md#troubleshooting) covers the
+   common failures of `initialize` and `record_payment`.
+
+## Where to report
+
+Open an issue on **https://github.com/bridgelet-org/bridgelet-core/issues**:
+
+- Start the title with **`[testnet]`**, for example
+  `[testnet] execute_sweep returns #2003 for funded ephemeral account`.
+- Add the **`testnet`** label. If you can't set labels, the `[testnet]`
+  prefix is enough and a maintainer will apply the label.
+
+Keep this separate from general contract-development issues:
+
+| Your problem | Where it goes |
+|---|---|
+| The deployed testnet contracts, IDs, config or behavior don't match the docs | `[testnet]` issue + `testnet` label |
+| A bug in contract source, tests, build scripts or a feature request | Regular issue, no `testnet` label |
+| A possible security vulnerability, on any network | **Do not open a public issue.** Contact the maintainers privately (see below). |
+
+## What to include
+
+Copy this into the issue body:
+
+```markdown
+**What I tried:** (function name, e.g. SweepController::execute_sweep)
+**What I expected:**
+**What happened:** (full error, e.g. `Error(Contract, #2003)`)
+
+- Contract ID(s) called:
+- Transaction hash (if submitted):
+- Ephemeral account contract ID (if relevant):
+- Approximate ledger / UTC time:
+- Client: stellar-cli vX.Y / @stellar/stellar-sdk vX.Y / other
+- Network passphrase used:
+```
+
+A transaction hash is the most useful single detail. You can look it up on
+https://stellar.expert/explorer/testnet, and it lets a maintainer reproduce
+the exact call.
+
+**Never post secret keys (`S...`) or signing-key material**, even for
+throwaway testnet accounts.
+
+## Security issues
+
+If you think you've found a vulnerability, such as a sweep going to an
+unauthorized destination or a bypass of signature verification, report it
+privately. Use GitHub's **Report a vulnerability** button on the repository's
+Security tab. Do this even if you only reproduced it on testnet, because the
+same code is intended for mainnet.
+
+## Response expectations
+
+Testnet support is best-effort and handled by the maintainers. No response
+time is guaranteed. Issues that block several integrators, such as a testnet
+reset that leaves the deployment empty, take priority.