# Humand porting status

## Goal

Port the Humand workflow layer into this Pi setup without changing generic non-Humand behavior.

## Runtime model

- Activation gate: Humand repo/worktree only
- Detection: cwd under `/home/sebas/work/humand` or git remote containing `HumandDev` / `sfavaron-hu`
- Bootstrap source: `/home/sebas/pi-config/humand/workflow-setup.sh`
- Pi runtime entrypoint: `/home/sebas/pi-config/extensions/humand-mode.ts`
- Shared helper: `/home/sebas/pi-config/extensions/_shared/humand-shared.ts`
- Upstream source plugin: `/home/sebas/work/humand/hu-ai-agent-plugin/plugins/humand-tech`

## Ported now

### Bootstrap / context

- Humand mode detection by cwd/origin
- Bootstrap env load from `workflow-setup.sh`
- Humand prompt injection: `HUMAND.md`
- Session notice via `session_start`

### Tools

- `humand_context`
- `humand_status`
- `humand_feature_resolution`
- `humand_start_feature`

### Commands

These slash-style commands are registered by the Pi extension and dispatch into the matching loaded Humand skill:

- `/start`
- `/status`
- `/pr`
- `/merge-watch`
- `/summary`

### Skill loading

In Humand context, the extension exposes upstream Humand skill resources from:

- `/home/sebas/work/humand/hu-ai-agent-plugin/plugins/humand-tech/skills`

This is how the command flows above resolve their matching skills.

## Intentionally partial / not wired as runtime hooks

### Upstream hook reference

- Reference file: `/home/sebas/pi-config/humand/hooks/session-start`
- Status: copied for reference only
- Not auto-executed by Pi runtime on this machine
- Real activation path here is: `humand-mode.ts` + Humand bootstrap + loaded Humand skills

### Not fully ported as first-class native Pi features

These upstream workflows still run through skill instructions, not bespoke local reimplementation:

- `/start`
- `/status`
- `/pr`
- `/merge-watch`
- `/summary`

That is acceptable for current scope as long as the commands and skills load correctly in Humand context.

## Validation checklist

- [x] `pi` starts with Humand extension enabled
- [x] Humand bootstrap vars resolve
- [x] Humand tools answer in Humand repos
- [x] Humand skill path is injected in Humand repos
- [x] Skills `skill:start`, `skill:status`, `skill:pr`, `skill:merge-watch`, `skill:summary` appear in session command inventory
- [x] Commands `/start`, `/status`, `/pr`, `/merge-watch`, `/summary` register in Pi command inventory
- [ ] Interactive session-start notice visually confirmed in TUI
- [ ] End-to-end behavior of every upstream workflow validated against external deps

### Validation evidence

Validated in `/home/sebas/work/humand/humand-web`:

- `humand_context` returned `active=true`
- `humand_status` returned configured/existing repo coverage
- bootstrap env exposed Humand config/state/local-config vars
- RPC `get_commands` showed:
  - `start`
  - `status`
  - `pr`
  - `merge-watch`
  - `summary`
  - `skill:start`
  - `skill:status`
  - `skill:pr`
  - `skill:merge-watch`
  - `skill:summary`

## Notes

- Do not place helper modules as top-level files in `extensions/` unless they export a real Pi extension factory. Pi auto-loads top-level extension files.
- Keep Humand-specific runtime surface gated by Humand detection so Ballbox/personal sessions stay unchanged in practice.