Skip to content

Known limitations and unwired code register #638

Closed

Description

@codebestia

Branch: Open your PR against dev. PRs targeting main are closed automatically.

Description:
Write docs/known-limitations.md: a maintained register of code that exists but is not live, behaviour that is deliberately incomplete, and hardcoded values awaiting configuration. Without it, contributors build on stubs or "fix" deliberate limits.

Acceptance criteria:

  • Each entry: description, location, impact, and the issue tracking it (open one if none exists)
  • Seeded with at least these items found while scoping this batch: auditLogsRouter not mounted in app.ts; the hardcoded AI agent URL in socket/messaging.ts; ratchetSession.ts not wired into the app and rejecting out-of-order messages; Phase1SessionCrypto as the live default rather than Signal; inconsistent API URL defaults in apps/web; and orphaned server-style files in the web app (apps/web/src/service/cacheService.js, apps/web/src/app/routes/conversations.js) plus src/components/ui/WalletAddress.tsx and apps/tests/ at the repo root
  • States the rule that an entry is removed in the same PR that resolves it
  • Linked from CONTRIBUTING.md and the documentation index (Safety-number verification UI reconciled onto the surviving route #359)

Activity

  1. beatriceaina04-maker commented on Oct 20, 2026

    @beatriceaina04-maker

    @beatriceaina04-maker has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hi! I've gone through the requirements carefully and I'd love to take this on. I'll make sure the solution meets all the stated criteria.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @beatriceaina04-maker to this issue.

  2. omarima-10 commented on Oct 20, 2026

    @omarima-10

    @omarima-10 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I would like work on this issue.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @omarima-10 to this issue.

  3. drips-wave commented on Oct 20, 2026

    @drips-wave

    Congratulations, @omarima-10! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @omarima-10: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. github-actions commented on Oct 22, 2026

    @github-actions

    Closed by #682, merged into dev.

  5. drips-wave commented on Oct 22, 2026

    @drips-wave

    This issue has been completed by @omarima-10 as part of the Stellar Wave Program's 10th Wave 🥳

    😎 @omarima-10: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programdocumentationImprovements or additions to documentationdx

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions