[armando-navarro]

Checklist

• Issue number for this PR: Recommended API Version #3336
• Docs included?: yes, this is a docs-only change.
• Test units included?: no, Markdown only.
• Breaking change?: no.
• In a clean directory, yarn install, yarn test run successfully? Not run, the change is two Markdown files. npm run lint passed.

Description

docs/compat.md never said whether @angular/fire/compat is supported, and the v7 upgrade guide still told readers to stop at the compatibility API because the modular API "isn't feature complete", a sentence from the 7.0 release. #3336 asked for a direct answer in 2023 and never got one. This writes the answer down.

Changes

• docs/compat.md gets a "Support status" section: the compatibility API is still supported, gets bug fixes but no new features, and has no planned removal. A second paragraph says which of its tests are turned off and links Restore the skipped compat Firestore and Storage specs #3822, which tracks turning them back on.
• docs/version-7-upgrade.md: the bolded line becomes "You can stop here if the compatibility API covers your needs.", followed by the support summary and a link to the new section.

Fixes #3336

[tyler-reitz]

The support section says the compatibility API "is kept working on every Angular and Firebase version AngularFire supports", but CI doesn't currently check that for compat Firestore. All 48 skips in the browser run (Executed 112 of 160 (skipped 48)) are compat specs: collection, collectionGroup and document under src/compat/firestore/ are skipped wholesale by a beforeEach pending("These are pretty broken, investigate."), in place since #3586, plus one storage upload spec.

Could the section either qualify the promise for those APIs, or link an issue tracking the skipped specs? Otherwise the first reader whose collectionGroup query breaks on an upgrade will find the docs promised it worked.

[armando-navarro]

Did both: the section now says which tests are off and links #3822, which tracks turning them back on.

[tyler-reitz]

When you squash, please trim the first commit's body out of the message: it still says the compat specs "run in the same test suite as the modular API" and that the API is "kept working", which the second commit corrects.