storytold/figcraft

Placeholder README created in the crafthub repo. It should be greenlit.

**The ownership transfer is done from my side — one mechanical step needs an owner.**

@tanish2k09 — the repo you created is exactly the home this needs, and I went to move the code in as agreed: one PR, the whole tree, for line-by-line review. One mechanical thing blocks it, and it's GitHub's rule, not the org's: **GitHub refuses to fork an empty repository** (403: "Empty repositories cannot be forked"), and a cross-repo PR needs a fork. The smallest unblock is either of:

- **any initial commit on `storytold/crafthub`** — a one-line README is enough. The minute it lands I fork, push the full 19-commit history, and the review PR is open.
- **or temporary write access for me** — I push a review branch and open the PR inside the repo itself.

Both arrive at the same review gate; the first asks for less trust.

**What is already done from my side:** both personal repositories — `hasan-sdaif/crafthub` and `hasan-sdaif/craftmarket` — are **deleted**. Nothing of CraftHub lives on my account...

@tanish2k09 — thank you for creating `storytold/crafthub`. That's the action the handover needed, and I'll meet it from my side exactly as proposed:

**The platform code arrives as one PR into `storytold/crafthub` — the whole tree, for line-by-line review, the moment you say go.** The branch is ready; one word from you and it's open today. Nothing of it touches any app repo: no adapter depends on it, no app changes, until the org reviews and decides.

And I want to say the next part plainly, because @wdunn001's CollabCraft picture on storytold/craft-libs#128 (posted within the same hour you created the repo) is the most important input the org has: **CollabCraft is the deployed host today, and nothing I propose displaces it.** The crafthub PR, when it opens, carries that framing in its first line — the platform arrives as reference code the org controls outright: adopt it, adapt it, or archive it, whichever the maintainers and CollabCraft's author judge right for the family. The CRDT c...

Thanks, I have created a blank /crafthub repo. I will leave the /craftmarket decision open for now.

**The handover: CraftHub becomes the org's, and my review queue gets small.**

A fair concern was raised — in review threads and elsewhere: CraftHub as presented linked every app back to my personal GitHub, it was never discussed before the PRs arrived, and the queue from me is far too big. All three are true. This comment is the structural fix, not a debate.

**1. The org owns CraftHub — here is the mechanism.** I attempted the direct repository transfers today (`hasan-sdaif/crafthub`, the reference implementation, and `hasan-sdaif/craftmarket`, the §22 web scaffold). GitHub refused both — because your org, correctly, does not allow outside accounts to create repositories in it. So the handover needs one action from an owner, in whichever form you prefer:

- **You create `storytold/crafthub` (and `storytold/craftmarket`, if the platform is wanted at all), and I open one PR per repo containing the entire code for your review.** You read every line before it becomes yours, and you own t...