# FreENxt beta tester guide

FreENxt is beta software. Test with an exported **copy**, never your only or
original data. Keep the source export unchanged until you have inspected the
downloaded vault and conversion report.

## Who this guide is for

This guide is for **invited testers only**. Testing access is by invitation; do not redistribute this guide as a general sign-up. Use a copied export or synthetic sample — never the only copy of a vault.

## Recommended tester profile and cohort

Start with 8–12 invited testers who can export data, inspect Markdown and ZIP
files, compare links and attachments, and file a reproducible report without
sharing private note content. Include current Chrome/Edge (Chromium) and
Firefox testers, with a mix of Evernote, Notion, local Markdown, and one or two
additional sources. **Safari and iPad are not represented as supported
platforms.** If a tester uses Safari or another untested browser, request they
report the browser name and exact version — do not represent it as a supported
path. Expand only after the first cohort completes sample conversions without
data-loss findings.

Use 5–20 representative notes first. Include plain text, tags, internal links,
nested pages, and a few attachments. Do not begin with a complete or
irreplaceable archive.

## First conversion

1. Export from the source app, preserve that export, and make a separate test
   copy.
2. Open `https://freenext.app/workbench/` and choose the source type matching
   the file or folder label shown in the workbench.
3. Keep unsafe attachment neutralization enabled unless that option is the
   specific subject of the test.
4. Convert and download `obsidian-vault.zip`.
5. Extract it into a new empty folder. Do not merge it into a production vault.
6. Compare note counts, titles, folders, links, tags, dates, frontmatter, and
   representative attachments against the source copy.
7. Review `manifest.json` and the on-screen conversion report for warnings,
   unsupported features, unresolved links, and attachment counts.
8. Repeat with a larger copy only after the sample is correct.

## Privacy and consent

The browser workbench processes selected file content in the browser tab and
does not upload that content to FreENxt. Optional analytics and diagnostics
remain off unless the visitor grants consent. Lead-capture email is optional
and separate from conversion.

Do not put note text, private filenames, email addresses, credentials, license
files, or screenshots of private content in a report. Use aggregate conversion
counts or a synthetic reproduction file.

The 7-day trial starts after the first successful conversion and is stored in
that browser profile. Clearing browser storage, private browsing, or switching
profiles can affect local trial state.

## Known beta limits

- Commerce is not required for beta acceptance. Do not make a real purchase
  unless the beta coordinator confirms the checkout is live.
- Bitcoin/Lightning and fiat support paths may be unavailable while provider
  configuration is staged. Code presence is not proof of live deployment.
- Encrypted, proprietary, or source-omitted content may be reported as
  unsupported.
- Browser downloads target an Obsidian-style Markdown vault.

## Reporting and recovery

Use the repository's **Beta feedback** issue form and include the release SHA,
operating system, browser/version, source type, checklist step, expected and
actual behavior, and a redacted error message. Repository access may be
required.

If conversion fails, leave the original export untouched, close the tab, retry
with a fresh copy and smaller sample, and report whether the failure repeats.
General project support links are in [`docs/support.md`](support.md).