Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

Address review: pin the fork's identity, finish the README repointing

Four items from the review on #3:

1. "Linking both drivers" documented the errors.As type-identity hazard but not
   the one that mirrors this PR's own thesis: with both drivers linked, a call
   site still saying sql.Open("mysql", ...) resolves to upstream and keeps
   working, until something reaches for QueryResultContext or Warnings()
   through (*sql.Conn).Raw. Everything else in the both-linked surface fails
   loudly (the registries are package-level globals and name the cause on use),
   so the one silent case is worth naming.

2. Nothing pinned the two lines this PR consists of. Both mutations — the
   driver name back to "mysql", the module path back to upstream's — build
   clean and pass the full suite, and they are exactly the two places every
   `git merge upstream/master` has a conflict to resolve. fork_test.go asserts
   both: debug.ReadBuildInfo().Main.Path reads the real go.mod rather than a
   copy, and sql.Drivers() reads what init actually registered. Verified it
   kills both mutations.

3. The LOAD DATA LOCAL INFILE section still had `import
   "github.com/go-sql-driver/mysql"` — the one copy-pasteable import left on
   the old path, in the section whose premise is needing the package directly.
   Following it registers a local file in upstream's fileRegister while
   connections come from block-mysql. Its godoc link now points at the fork,
   which documents the fork's additions too; the remaining upstream links are
   provenance and stay.

4. "5 CI jobs rather than 25" was wrong. Ran the workflow's matrix generator at
   both revisions: 21 base combinations + 2 appended include entries = 23 test
   jobs before, 3 + 2 = 5 after.