Skip to content

Expose the enabled common semantic map on the standalone landing page #915

Description

@realmarcin

The common semantic-map integration being prepared for #910 adds a conditional link in templates/base.html, but the homepage uses standalone templates/index.html. A full enabled preview renders and validates all 306 points yet its landing page contains no link to text-map/.

Evidence: the isolated preview at baseline 6d5b07dc3f99d5f29dd9b0c939d1f481a83eb049 plus integration commit e44d0399dcf5bb880e9ee759d2be6e689a8502be and the reviewed 512-token policy fix stages the verified current BGE/PaCMAP bundle, and every point target resolves. The existing MiniLM map and neighbor artifact hashes remain unchanged. The landing assertion fails because the standalone template does not inherit the new navigation.

Acceptance:

  • Show a direct semantic text-map entry on the homepage only after enabled, validated staging.
  • Preserve and clearly distinguish the existing MiniLM/PCA view.
  • Test both enabled and disabled homepage rendering, and verify the actual full site and all point links.

This is a pre-merge integration finding under CultureBotAI/culturebotai-claw#426, discovered during full preview verification; it does not assert that the pending common map is already deployed.

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