Repository navigation
docs: checkpoint community store direction and repository ownership - #33
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The store and website repositories contain competing storefront implementations, while the latest discussion sets a shared public identity and hosted development preference. This PR makes that context discoverable without choosing a migration or activating hosting.
Adds a current handoff and dated discussion checkpoint; updates AGENTS, README, META, ROADMAP and routing/architecture pointers; adds ADR-004 while preserving ADR-003 and marking the cross-repository conflict. The website owns the full launch-plan and proposed milestone/sub-issue map.
Companion website PR and canonical plan: egohygiene/egohygiene.io#74
Proposed milestone hierarchy: https://github.com/egohygiene/egohygiene.io/blob/docs/store-launch-direction-20261016/docs/roadmaps/store-launch.md
Next step is maintainer review. Proposed issues/milestones will be created or reorganized only after approval, then we sync again. No deployment, provider activation, purchase, repository transfer, migration, or issue creation occurs in this PR.
Validation: relative link targets checked against the complete source tree; available local anchors, Markdown fences and endings checked; independent review completed; remote compare confirms nine intended Markdown changes. The combined documentation check covered 142 relative links. Runtime/browser/provider tests were not rerun; existing dependency PRs #26/#27 remain untouched.
2026-10-17 merge checkpoint: maintainer authorized merging the planning PRs and beginning the first ownership-reconciliation issue. Refreshed head 39a478e; comparison contains only nine intended Markdown files. Quality gates pass; E2E still fails on the existing ambiguous getByText("Black / Small") locator, tracked by #32. No check, setting, or protection is bypassed or disabled.