TBD/DWN changes and strategy

# Overview

This issue tracks how we handle the TBD transfer. This breaks into 2 major categories:
1. High-priority near-term changes required: this is informed by the requirements of the transfer agreement, but also community continuity
2. Longer-term strategy for health

I'll start with the high-priority near-term changes

## High-priority near-term changes

### Requirements per transfer agreement

1. Maintenance and Updates
- Must use "commercially reasonable efforts" to maintain and update the open-source version of the materials according to industry best practices
- This includes facilitating updates and bugfixes, providing improvements, and receiving/incorporating community contributions
- Must obtain proper legal documentation from contributors
2. Open Source Requirements
- Must provide the materials to the general public under the Apache 2.0 license on an ongoing basis
- Must make "commercially reasonable efforts" to provide improvements via the GitHub repository
- If DIF fails to comply with these open source requirements for 30 days after notice from Block, Block can:
- Have the rights revert back to them
- Provide the materials to the public themselves under an open source license of their choosing
3. Attribution and Branding:
- Must promptly remove Block's trademarks, logos, trade names, and other identifying marks from the software and materials (except for standard attribution notices in source code)
- Must comply with any future requests from Block to remove or retain specific identifying materials
4. Export Control: Must comply with US export laws and regulations

While DIF is required to maintain the repositories, the agreement uses the standard of "commercially reasonable efforts," which provides some flexibility in how these obligations are met rather than requiring specific metrics or standards.

### Summary of near-term issues
- [ ] did-dht.com is locked until 1/25; will be transferred afterwards (right now, site is down)
- [ ] The cross-cutting issue is with documentation
- Github instructions reference tbd org, but not urgent -- those redirect nicely
- Need to check all website links
- Need to republish npm packages or other?
- Per requirement 3, I don't see Block branding on a spot-check, but can we double-check?
- [ ] Community: discord community was transferred over, but are we promoting successfully?
- [ ] Anything else? Do we need some near-term outreach, messaging? Who can help with this?

Start by reviewing the GitHub instructions and checking the website links mentioned in the checklist. Then investigate whether npm packages need republishing and whether any Block branding remains. Done is not defined beyond resolving the listed transfer, documentation, community, and outreach questions.

Written by the indexing model from the issue text.