Skip to content

Restrict new publication convergence to top-level commands #880

Description

@bcdonadio

Observed behavior: The new preAction branch checks only action name install/doctor. Nested lcm connectors install also matches and gains identity probing and bounded retry beyond the approved top-level install/doctor scope. Existing lock exclusivity remains unchanged.

Expected behavior / safe remediation: Add a top-level parent check. With mocked command services, assert connectors install still migrates but never builds the new convergence or probes health. Related #866 tracks deliberate broader command convergence.

Evidence: Static review of Bug #783 candidate 5668f1c6c7bef61dc25db8ef2ed6bb06e96e2211, bin/lcm.ts:4035-4061. Accepted as P2 by independent-review synthesis and owner. No live installation, daemon, or exploitation reproduction. Candidate has not been published as a PR yet; link will be added at publication.

How to reproduce safely: Use the injected/private-fixture test described above against the named source path; do not manipulate live HOME or daemon locks.

Environment:

  • Agent: Opus 5 medium adjudication, Astra owner
  • Connector: static repository review
  • OS: Fedora Linux

Discovered during #783 / Epic #848, finding F5. Separate deferred native Bug outside S0; does not block the issue-scoped candidate.

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

    Fields

    Priority

    Medium

    Effort

    None yet

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions