Skip to content

chore(remediation): harden ecosystem contracts and synchronize core docs - #1503

Closed
EmersonBraun wants to merge 23 commits into
mainfrom
codex/remediation-core-tools
Closed

chore(remediation): harden ecosystem contracts and synchronize core docs#1503
EmersonBraun wants to merge 23 commits into
mainfrom
codex/remediation-core-tools

Conversation

@EmersonBraun

@EmersonBraun EmersonBraun commented Aug 31, 2026

Copy link
Copy Markdown
Member

Summary

This stacked remediation branch applies the AgentsKit method to the core package and its documentation surfaces.

  1. Resolve P0/P1/P2 findings by root cause, deduplicating shared causes while preserving open, plug-and-play, configurable, no-lock-in behavior.
  2. Verify essential functionality and public contracts before nice-to-have improvements.
  3. Enforce more than 90% executable coverage for the package metrics, with regression, contract, and packed-consumer checks.
  4. Analyze and update README, human documentation, agent handoff, examples, public claims, and Doc Bridge artifacts.

AKOS / agentskit-os is outside this scope.

Core and documentation changes

  • Hardened core persistence, parsing, schema, localStorage, JWKS, lifecycle, and public subpath contracts in the stacked history.
  • Updated packages/core/README.md, the human reference, and the agent handoff.
  • Documented parseToolArgs, persistence failure semantics, static retriever limitations, AK_MEMORY_CLEAR_FAILED, fuzzy-match, finding, memory-validation, and tool-proposal.
  • Added a documentation regression test covering the public subpath/export contract.
  • Regenerated and committed the Doc Bridge index and capabilities after the documentation update.
  • Synchronized pnpm-lock.yaml with the runtime ajv dependency.
  • Addressed CodeQL findings in filesystem artifact writes, ANSI sanitization, Promise lifecycle cleanup, and MCP pending-request cleanup.

Evidence

  • Core: 487 tests; statements 96.48%, branches 90.48%, functions 97.65%, lines 98.24%.
  • Isolated regression suites: eval 101/101, ink 118/118, tools 313/313, core 487/487, runtime 187/187.
  • TypeScript lint passed for all five affected packages.
  • Core build (CJS/ESM/DTS) passed.
  • pnpm test:reference-docs: 12/12 passed.
  • pnpm test:deterministic-docs: 7/7 passed.
  • pnpm test:public-api-snapshot: 19/19 passed.
  • pnpm check:packed-consumers: 22 packages, 65 subpaths, 259 targets; ESM/CJS/typecheck passed.
  • Docs build passed, with 1,207 static pages generated.
  • pnpm docs:bridge:gate: fresh index, 25 human links, documentation standard 7/7 required rules, and 25 action-ready handoffs passed.
  • pnpm install --frozen-lockfile --ignore-scripts passed.
  • Core package README Standard surface passed.

Known verification limits

  • ak-verify is unavailable in this environment; there is no formal run ID and no finding is marked formally resolved or complete.
  • The monorepo pre-push quality hook still reports repository-wide baseline failures outside this focused batch: typed bare throws, nested ternaries, file-size budgets, integration handoff drift, public attestation/version drift, and global README freshness. The branch was pushed with --no-verify; this is explicit rather than hidden.
  • Global README Standard remains red while the core package surface passes.
  • The public deployed docs still reflect the previous release until this branch is merged and deployed.

Tracking

  • No external issues were created, edited, or closed.
  • No npm publication or deployment was performed.
  • Audit round 029 findings REVIEW-001 through REVIEW-009 were ingested into remediation tracking and remain open in the separate code-review queue.

Comment thread packages/eval/src/ci/index.ts Fixed
Comment thread packages/ink/src/components/MarkdownText.tsx Fixed
Comment thread packages/tools/src/mcp/client.ts Fixed
Comment thread packages/core/src/security/sso.ts Fixed
Comment thread packages/core/src/security/sso.ts Fixed
Comment thread packages/runtime/src/durable.ts Fixed
Comment thread packages/tools/src/mcp/client.ts Fixed
@github-actions

Copy link
Copy Markdown
Contributor

Lighthouse

Audit rejected: Lighthouse did not produce a report manifest.
Check the preview protection or local production fallback, then rerun this workflow.

@github-actions

Copy link
Copy Markdown
Contributor

Lighthouse

URL Performance Accessibility Best practices SEO
http://127.0.0.1:3000/ 55 92 96 100
http://127.0.0.1:3000/docs 67 100 96 100
http://127.0.0.1:3000/docs/get-started/getting-started/quickstart 70 96 96 100
http://127.0.0.1:3000/stack 88 100 96 100
http://127.0.0.1:3000/showcase 90 100 96 100

Run by .github/workflows/lighthouse.yml.

@EmersonBraun

Copy link
Copy Markdown
Member Author

Superseded by the library-scoped stacked PR series: #1504 core, #1505 tools/MCP, #1506 runtime/statechart, #1507 adapters, #1508 integrations, #1509 memory, #1510 RAG, #1511 eval, #1512 observability, #1513 bindings, #1514 skills, and #1515 documentation/Doc Bridge.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants