Improve the sqlite3 reference, using Diataxis as a guideline. A lot of work has already been done here, with great help from Alex Waygood and CAM Gerlach. PRs so far¹ have focused on...:

• Be accurate
• Do nothing but describe; making the wording more to the point

There are remaining issues, though:

• Be accurate:
  • gh-95273: Improve sqlite3 class descriptions #95379
  • gh-95273: Clarify when the sqlite_* attributes are added to sqlite3 exceptions #95523
  • gh-95273: Improve documented return values and exceptions raised for sqlite3 class methods #95530
• Be consistent: Most of the reference docs for sqlite3 functions and methods use the imperative mood. Some of the methods use other wordings. Suggesting to normalise, and use the imperative mood across the reference section.
  Improved with:
  • gh-95273: Normalise sqlite3 reference wording #95274
  • gh-95273: Align sqlite3 const refs with the devguide #95525
  • Remove duplicate links
• Respect the structure of the machinery: Arrange the sections of reference to follow the architecture of the module. This is pretty good already, but I believe we may benefit from some adjustments, in particular:
  • Consistently group attributes and methods
  • gh-95273: Reorganize sqlite3 doc module level funcs and vars #95626
  • gh-95273: Relocate sqlite3 enable load extension note #95430
  • Align wording in function and method docstrings with documentation
• Do nothing but describe: Avoid digressions and discussions, or even better, extract them to separate sections. Remove and or simplify examples.
  • gh-95273: Move sqlite3 executemany examples from reference to tutorial #95351
  • gh-95273: Condense sqlite3 executescript example #95383
  • gh-95273: Improve sqlite3.complete_statement docs #95840