Skip to content

Exercise both community and isolate roots in the common-map renderer regression #909

Description

@realmarcin

The new common-map renderer regression in tests/test_text_map_site.py chooses its fixture by globbing only kb/communities. CommunityMech's full declared suite correctly rejects that undeclared single-root sweep: test_every_sweeping_test_declares_its_scope fails, with 3,235 other tests passing and 99 skipped.

The production integration already renders current community and isolate targets, but the new regression does not exercise the isolate half of that contract. The right fix is to use the shared record-root definition and include a real isolate fixture, then assert its generated detail page alongside the community page and common/specialty navigation. Do not add a scope exception or relax the existing guard.

Acceptance: the root-coverage guard and all common-map renderer/publication tests pass, with both corpus roots exercised. Re-run check-docs-current after committing the reviewed generated site because its current dirty-tree failure includes intentionally uncommitted integration files.

This is part of CultureBotAI/culturebotai-claw#426. Existing current open text-map issues were checked: #907 covers quoted recipe arguments and does not cover this regression gap. Detailed failure evidence is in workspace/embedding-remediation-20260915/required-validation/communitymech/test.log.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions