Skip to content

feat(diagnostics): publish framework-neutral package subpath - #282

Draft
seonghobae wants to merge 25 commits into
feat/writing-diagnostics-collaborationfrom
feat/writing-diagnostics-package
Draft

feat(diagnostics): publish framework-neutral package subpath#282
seonghobae wants to merge 25 commits into
feat/writing-diagnostics-collaborationfrom
feat/writing-diagnostics-package

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Stack boundary

This Draft is the existing package-surface owner stacked on current #281 feat/writing-diagnostics-collaboration@14a01a8c95b4dcdc14bbcb04c4c5ed0476a857ba. Current exact head is feat/writing-diagnostics-package@03e626e57c9b85d5f6cc9b616249b09bdf1669e2. Protected shipped truth remains main@3b38ead2d00f44eb578d0689087b9293b3dabe1e while release issue #118 freezes v0.6.0 publication.

The parent-only Semgrep-classification repair was synchronized non-destructively through the existing stack. Earlier synchronization SHAs do not describe the live stack and their workflow evidence does not transfer.

Product / package surface

This lane packages the already-verified host-supplied writing-diagnostics contract through a framework-neutral public subpath without expanding Inkspan's semantic authority or introducing model/provider/service ownership.

  • explicit @contextualwisdomlab/cwl-editor/writing-diagnostics export map;
  • ESM and CommonJS bundles plus declarations and sourcemaps;
  • strict bounded diagnostic validation, redacted error types, structural text projection and W3C text-position selector resolution;
  • dedicated declaration/build configuration and real packed-tarball ESM/CommonJS/SSR/TypeScript consumers;
  • package scans reject external runtime authority, dynamic loaders, ambient network/credential access, and UI/collaboration runtime dependencies.

The emitted subpath does not initialize React UI, browser DOM, Yjs/provider/awareness state, model providers, network clients, credential stores, persistence adapters, Naruon, contextual-orchestrator, or email/thread/recipient context. Inkspan does not generate grammar, tone, clarity, pragmatics, technical-quality, or actionability judgments.

Exact-current-head evidence

At the latest pre-write refetch:

  • PR is open, Draft; exact head is 03e626e57c9b85d5f6cc9b616249b09bdf1669e2;
  • live predecessor feat(diagnostics): add collaborative writing-guidance parity #281 is exactly 14a01a8c95b4dcdc14bbcb04c4c5ed0476a857ba and the current base snapshot follows it;
  • PR-triggered workflow lookup for this exact head returns no generation, so required exact-head workflow evidence is absent/non-passing; predecessor/push/status evidence cannot substitute;
  • formal submitted reviews: 0;
  • unresolved inline review threads: 0;
  • qualifying independent approval: 0.

The missing PR generation remains bounded by the existing stacked-PR trigger/dispatch owner path (#298/#299); do not create a competing CI writer here. #285 owns downstream hostile-input, browser and release-provenance assurance.

Integration boundary

Keep Draft/unmerged while #281 remains the exact predecessor and #118 freezes publication. Before any lifecycle transition independently refetch current #281 head, #282 exact head, ancestry, required repository/central workflows, live governance, formal reviews and threads. Pending/queued/skipped/cancelled/absent/neutral/failed/stale/predecessor/status-only/model-only evidence is non-passing. Do not self-approve, force-push, destructively rebase, transfer predecessor evidence, weaken gates, create release identity, or bypass protection.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@opencode-agent opencode-agent Bot added the type: feature New or expanded product capability label Aug 22, 2026
@seonghobae

Copy link
Copy Markdown
Contributor Author

#282 was restacked onto the current #281 head 7fe4886.

Exact head: 643baed

Verification on that tree:

  • package contract tests: 4 passed
  • TypeScript typecheck passed
  • full Vitest coverage: 187 files, 1052 tests passed; all four metrics 100%
  • all package entrypoints built, including writing-diagnostics ESM, CommonJS, and declarations
  • isolated packed-package consumers passed for ESM, CommonJS, SSR, and strict TypeScript
  • demo production build passed
  • effective PR delta remains the intended eight files
  • hosted head/base OIDs and files re-fetched after push; mergeable is MERGEABLE

Checks are queued before runner assignment.

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

…ration' into feat/writing-diagnostics-package
@seonghobae seonghobae added the enhancement New feature or request label Sep 7, 2026 — with ChatGPT Codex Connector
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request priority: medium Normal-priority or P2 work status: draft Draft pull request type: feature New or expanded product capability

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant