i think it could be brought to FINAL if there are no objections remaining. of course being FINAL doesn’t mean the .htaccess redirects can’t be updated in the future; the scope of this proposal is simply to have the redirects be managed by w3id.
in a practical sense we have some feedback from @eprodrom that codeberg’s reliability has been somewhat low. if there are better destinations to host a copy of the repo, now would be the time to suggest them. a deploy hook could be configured on the fep repo to deploy fep resources to that host.
i don’t think there needs to be any separation between formats; rather, each fep gets its own folder to include whichever resources it wants to include. at minimum, a fep-xxxx.md can be rendered into an index.html, and most likely a jsonld file that can be used as a context document (which fep authors can locate anywhere within the fep folder, but the two approaches that make the most sense are to either call it something like context.jsonld or to otherwise use the fep-xxxx.jsonld to serve both a @context and a @graph in the same document)