BDD style user stories are not good documentation. I’ve never seen them used by anybody but the developers after a feature build even on teams that used BDD and maintained them as live specs.
They were just more cumbersome alternatives to functional tests, and due to tooling costs, they were always augmented by other kinds of functional tests anyway, so the layman-readable bits were always incomplete.
Because they were too high-level, they were also not good documentation for developers trying to diagnose test failures. Reading the DSL always led to digging into the underlying implementations, a process that took much longer than it does with normal functional tests.
Lots of overhead to maintain “documentation” that didn’t serve anybody.