Skip to content

One entry predicate module #46

Description

@diegohb

Part of #44 — spec item 3.

One classifier module owns "does this plugin registration key entry name our package": spec parsing, scoped-name policy, case folding, path-form / file:/// entry resolution. Consumed identically by the suite's registration detector and both status paths.

The generated side receives it through the same mechanism as the rest of the machinery (byte-sync where identical; the core module after item 7) — never a second classifier.

Absorbs the scattered matching logic; drift becomes impossible to introduce on one side only.

Activity

  1. self-assigned this
    on Oct 10, 2026
  2. diegohb commented on Oct 10, 2026

    @diegohb
    MemberAuthor

    Implemented and merged to issue-44-rearch. Resolved by PR !51.

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

Metadata

Metadata

Assignees

Labels

ready-for-agentFully specified, ready for an AFK agent

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions