Skip to content

[docs]: reconcile zsh-lint parser guidance for installable packaging #803

Closed

Description

@ss-o

Description

The organization source knowledge/domains/tooling/zsh-lint-parser-front-end.md still states that it was reconciled against zsh-lint revision 7ff05091a5489becf32069db1738d38ec23c8fd5, and its contract link is pinned to that revision. zsh-lint PR 699 moves the parser fork into the root Go module under accepted ADR-0041, and the generated project consumer has to follow that source before #699 can adopt it.

Delivery renders a project link as consumer-relative only when it is pinned to the record's project_revision. Updating the approved record in knowledge/project-delivery.json to the tested revision while the source still names 7ff05091 would keep the old remote contract link in the generated consumer, so the source has to be reconciled and published first.

Scope, in two organization changes:

  1. Reconcile the source against tested zsh-lint commit f1c43fac9c8eadfc914a4af89a1beea11afca891: update the reconciled project revision and the contract link together, and link ADR-0041 where the fork's import prefix is explained. Keep the frontmatter, selectors, paths, invariants and namespace-neutral wording. Every path, command and symbol the source names was checked to exist at that commit. The Go AST and wiki sources are out of scope.
  2. After that change merges, update only the z-shell/zsh-lint parser record in knowledge/project-delivery.json to the merged source revision and blob, project revision f1c43fac, the current consumer blob and the complete rendered digest, validated with org-routing.py validate and verify-approved.

Generating the consumer and repinning Org Routing in zsh-lint #699 follow in that pull request. Merging #699, a zsh-lint release and consumer rollouts stay separate decisions.

Select the area that is associated with this issue.

Other

Self-service

  • I'd be willing to address this documentation request myself.

Have you read the Contributing Guidelines?

Are you familiar with the Contributor Covenant Code of Conduct?

Contact Details

This GitHub issue thread.

Activity

  1. self-assigned this
    on Oct 16, 2026
  2. added
    type:docsDocumentation-only work.
    area:docsDocumentation systems, content, or publishing.
    on Oct 16, 2026
  3. moved this from Triage to In Progress in Z-shell Deliveryon Oct 16, 2026
  4. moved this from In Progress to Done in Z-shell Deliveryon Oct 16, 2026
  5. ss-o commented on Oct 16, 2026

    @ss-o
    MemberAuthor

    Reopened: #804 delivered only the first of the two changes this issue describes. Its body mentioned the follow-up with a closing keyword, which closed this issue at merge. The approved delivery record update in knowledge/project-delivery.json remains and will close this issue.

  6. reopened this on Oct 16, 2026
  7. moved this from Done to In Progress in Z-shell Deliveryon Oct 16, 2026
  8. moved this from In Progress to Done in Z-shell Deliveryon Oct 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:docsDocumentation systems, content, or publishing.type:docsDocumentation-only work.

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions