Repository navigation
Conversation
why: Shared documentation needs the public record owners and actual defining sources while retaining native Haskell signatures. what: - Add a separate observation profile for the scoped Server and snapshots - Preserve module reexports and owner-scoped record fields - Validate compiled exports, native anchors and archived source text - Retain native inputs and preserve the qualified scalar profile
why: Duplicate record labels and facade reexports need their public context without changing native names or losing defining sources. what: - Adapt the qualified observation profile alongside scalar interfaces - Retain record owners, native links and ordered module reexports - Give the reexport root one navigation row without copied members - Reject incomplete modules and conflicting module identities
why: Public capture and recovery types need readable continuation lines within the API reference column limit. what: - Continue outer type arrows while preserving native links and tokens - Keep callback scopes, character literals and escaped strings intact - Leave unbreakable literals exact and report their width
why: The public observation API needs native reference ownership, checked source provenance and guides that use the same reviewed library revision. what: - Publish the Haddock observation model and authored navigation groups. - Stage capture, offline-fixture and performance guides from source. - Bind native command attribution to reviewed source and API metadata. - Exercise snapshot collection ordering and preserve excluded products.
why: Function and type references need declaration-level destinations so readers reach the named API with the correct language kind. what: - Resolve unique public labels within their declared module. - Prefer data heads for shared type and constructor spellings. - Preserve ambiguous labels and explicit source-fragment destinations.
why: Compiler extension references need checked destination identity alongside the package API links. what: - Record the owning GHC manual heading for record-dot syntax. - Capture the successful destination response and identity evidence.
why: The capture API adds an entry module and reverse references beyond the scalar API. Reference checks need to preserve that native structure. what: - Derive module sections from the current public model in its declared order. - Compare exported members within their own sections, excluding backlinks.
why: The capture reference now resolves more native cross-references. Preserve that coverage as the public API grows. what: - Raise the Haskell-only resolved-link floor from 300 to 1372. - Keep the unresolved-type ceiling at zero and other ports unchanged.
22 of 24 tasks
why: The public Runtime API needs reference pages and an installed guide that agree with the source consumers can build. what: - Refresh the native Haddock profile while retaining separate exporter provenance - Stage the shared Runtime guide and preserve every existing public signature - Bind queued command evidence and reference fixtures to the selected source
why: Shared Runtime declarations add native links that the reference regression check must retain. what: - Raise only Haskell's floor from the complete rendered reference - Keep the unresolved-type ceiling and other port baselines unchanged
why: The exact guide-path fixture omitted the shared Runtime page and rejected the complete public guide catalogue in CI. what: - Include the shared Runtime source and reader route in the guide contract
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Haskell now exposes scoped capture, detached observations, validated offline fixtures and shared Runtime ownership. This follows the initial Haskell registration in #265 and documents the public API in libtmux-haskell#4 using its native Haddock artifacts and committed reader guides.
Summary
Reference and source fidelity
The exporter preserves the scalar profile and adds an observation profile. Record labels retain their owning types, opaque declarations retain their public boundary, and private defining sources receive source links without private API pages. Native artifacts and library/exporter revisions remain independently bound.
The native command catalogue qualifies the complete library, C and package inputs, API metadata and public effect classifications. Capture receives reviewed entries for
display-message,if-shelland session-gatedlist-clients. Existing evidence, scope and drift checks remain active.Reader guides
Installation, capture, graph traversal, fixture validation, independent Server scopes, operational recovery and measured capture costs use committed native guides. Long type signatures wrap at valid Haskell boundaries. Collection ordering checks include the snapshot module’s ordinary functions.
Test plan
The clean selected-source build passed in 145.908 seconds; the final cache-backed assembly passed in 11.857 seconds. The publisher verified its 3,158-file inventory; the scoped Haskell-prefix audit checked 45,391 internal links with none broken. Sampled Chromium pages fit at 390, 768 and 1440 pixels, including the Runtime guide, public scope declarations and a dark-mode API page. The native graph fence currently displays as code on the shared site.
Haskell's resolved-reference floor rises from 300 to 1,468; its unresolved-type ceiling remains zero. Other ports' baseline rows are unchanged. Native module/member and guide-staging regressions pass. The installed shared Runtime program also passes from its pinned Git dependency on both tmux endpoints.
Full site and hosted publication qualification remain pending for the current head. The exact-head hosted run is in progress. The combined local outer run fails two PowerShell prose-audit five-second timeouts under the shared four-core, 8 GiB guard; that file passes in isolation. The site type check passes with an explicit 4 GiB Node heap within the same job cap. No test budget increase is included. One Elixir prerequisite check is skipped in the local API-model suite.
Companion PRs
haskell-portbranch until that PR lands.