Scaffold @agentworkforce/persona-kit package (1/8)

[willwashburn]

Closes #64.

Summary

Issue 1 of 8 in the persona-kit consolidation track. Creates an empty @agentworkforce/persona-kit package skeleton mirroring packages/harness-kit/'s layout. No code is moved and no functional changes occur — subsequent issues will fill the package in.

Changes

• packages/persona-kit/package.json — name @agentworkforce/persona-kit, version 1.0.0, type: module, ESM entry at dist/, publishConfig.access: public, same script set as harness-kit (build, dev, typecheck, test, lint).
• packages/persona-kit/tsconfig.json — extends the same tsconfig.base.json harness-kit uses.
• packages/persona-kit/src/index.ts — placeholder export {}.
• packages/persona-kit/README.md — short stub pointing at the tracking issue.
• pnpm-lock.yaml — refreshed (workspace registration is automatic via existing packages/* glob in pnpm-workspace.yaml).

No monorepo-level build orchestration changes were needed — pnpm-workspace.yaml already uses packages/*, and there's no turbo/nx/lerna/TS-project-references config to update.

Verification

• pnpm install resolves cleanly.
• pnpm --filter @agentworkforce/persona-kit build succeeds and produces dist/index.{js,d.ts} artifacts.
• pnpm -r build succeeds across the monorepo.
• pnpm -r typecheck passes.
• pnpm -r test passes (cli: 147/147; persona-kit: 0 tests, clean).
• No diff outside packages/persona-kit/ and the lockfile (harness-kit untouched, no publish).

Test plan

• pnpm install at repo root resolves
• pnpm --filter @agentworkforce/persona-kit build succeeds
• pnpm -r build succeeds
• pnpm -r typecheck passes
• pnpm -r test passes
• No diff outside scaffolded package + lockfile

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d1ea908-1ffd-410c-b284-d395c3f86376

📥 Commits

Reviewing files that changed from the base of the PR and between cae95cd and 8a9ebf1.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• packages/persona-kit/README.md
• packages/persona-kit/package.json
• packages/persona-kit/src/index.ts
• packages/persona-kit/tsconfig.json

---

📝 Walkthrough

Walkthrough

This PR scaffolds the @agentworkforce/persona-kit package skeleton in the monorepo. It adds package.json with ES module configuration and export mappings, tsconfig.json extending the shared base, an empty src/index.ts module entry, and a README documenting persona-kit's role in the persona instantiation lifecycle.

Changes

Persona-kit Package Scaffold

Layer / File(s)	Summary
Package Identity & Exports packages/persona-kit/package.json	Package configured as @agentworkforce/persona-kit with ES module type, main/types pointing to dist/, and exports["."] mapping to compiled JavaScript and TypeScript declaration files.
Publish & Build Scripts packages/persona-kit/package.json	Includes files array for distributable artifacts (dist, README.md, package.json), repository metadata, public publishConfig, and npm scripts for build, watch, typecheck, lint, and test.
TypeScript Configuration packages/persona-kit/tsconfig.json	Project configuration extends ../../tsconfig.base.json, sets rootDir to src and outDir to dist, and includes src/**/*.ts in compilation.
Module Entry Point packages/persona-kit/src/index.ts	Empty export {} statement marks the file as a module without introducing named exports.
Documentation packages/persona-kit/README.md	README header for @agentworkforce/persona-kit with one-sentence description of persona-kit managing the persona instantiation lifecycle and link to tracking issue #64.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

• [persona-kit 2/8] Move harness-kit + workload-router persona code into persona-kit (no behavior change) #65: Scaffolding the persona-kit package is preparatory to migrating persona-domain code into it as described in that issue.
• [persona-kit 3/8] Compose top-level persona-kit orchestration API #66: The package setup directly prepares the module structure needed for the top-level persona orchestration API planned in that issue.
• [persona-kit 5/8] Shrink @agentworkforce/workload-router (drop persona types, major bump) #68: Creating persona-kit supports the plan to consolidate persona-domain exports into persona-kit and refactor workload-router to consume them.
• [persona-kit 8/8] Publish @agentworkforce/persona-kit@1.0.0 + workload-router major bump #71: The package.json and publishing configuration align with the publish-focused setup in that issue.
• Consume @agentworkforce/persona-kit; rewrite spawnPersona to honor full persona schema relay#832: The scaffolded persona-kit package is the exact package that relay proposes to consume and integrate for persona instantiation.

Poem

🐰 A package born from empty air,
With config, types, and scripts fair,
Persona-kit now finds its place,
Ready for code at slower pace. 📦✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: scaffolding a new @agentworkforce/persona-kit package as part 1 of 8, which matches the PR's primary objective.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, explaining the package scaffold, file structure, verification steps, and constraints.
Linked Issues check	✅ Passed	All coding requirements from issue #64 are met: package.json and tsconfig.json mirror harness-kit structure, src/index.ts contains placeholder export, README.md stub added, workspace registration works via pnpm glob, and builds/tests verified.
Out of Scope Changes check	✅ Passed	All changes are in-scope and limited to scaffolding packages/persona-kit/ and pnpm-lock.yaml; no code was moved, no harness-kit changes, no functional modifications to existing packages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/submit-github-pr-K8I2u

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.