Skip to content

feat: reduce mandatory agent context and install reference docs - #116

Merged
vsem-azamat merged 2 commits into
mainfrom
improve/context-core
Sep 6, 2026
Merged

vsem-azamat merged 2 commits into
mainfrom
improve/context-core

Conversation

@vsem-azamat

Copy link
Copy Markdown
Owner

Summary

  • Reduce the mandatory method core; move command/configuration details into on-demand references while preserving authorization, TDD, review, freshness and completion rules.
  • Install managed reference documents into .stdd/reference/ and rewrite paths at generated-render boundaries for consumer skills, method and plugin skills.
  • Add reproducible phase-context measurements, explicit assumptions and regression coverage for clean installations and reference lifecycle.

Measured normal-path reading (UTF-8 bytes)

Cumulative start → implement → finish, deduplicated under the documented repository-profile assumptions:

  • Claude: 48,104 → 36,038.
  • Codex: 48,105 → 36,039.
  • pi: 48,138 → 36,072.

See docs/agent-context.md and scripts/measure-agent-context.mjs for pinned baseline, phase/incremental counts, conditional reads and reproduction. These are text-volume measurements, not token counts or evidence of model speed/cost improvements. Dynamic session-hook output and project-specific documents are excluded; plugin is not separately benchmarked.

Verification

  • Coordinator rerun: npm test — 829 tests, 825 passed, 4 skipped, 0 failed.
  • npm run check: exit 0, 14 warnings and 1 informational diagnostic.
  • npm run selfcheck: stdd check: OK.
  • git diff --check: passed.
  • Independent read-only review and follow-up: reference reachability and measurement issues corrected; no remaining material blockers. Review conducted outside the STDD review runner.
  • Tests cover clean Claude/Codex/pi installs, installed reference paths/content, manifest hashes, idempotence, upgrade from absent reference copies, drift detection and retirement, directive classification and generated consistency.

Documentation evidence

Docs updated first: method/README.md, method/reference-commands.md, method/reference-generated-state.md, method/reference-integration.md, playbooks/finish-change.md, playbooks/implement.md

Upgrade and boundaries

Re-run stdd init after upgrading so existing consumers receive .stdd/reference/. Plugin adoption retains the existing init prerequisite; updating only a plugin against an old initialized checkout does not install the new references.

Runtime gates, schema, verdicts, budget accounting and worker/native integrations are unchanged. No release, deployment or consumer installation performed.

@vsem-azamat
vsem-azamat merged commit 261d1a7 into main Sep 6, 2026
13 checks passed
@vsem-azamat
vsem-azamat deleted the improve/context-core branch September 6, 2026 05:38
vsem-azamat added a commit that referenced this pull request Sep 6, 2026
## Summary
Prepare `@stdd/cli` and `@stdd/plugin` 0.11.0 in a release-only PR.
- Align package/lock/plugin/runtime versions and regenerate all host
stamps and manifest hashes with existing hook targets preserved.
- Refresh README doctor proof and agent-context report version stamp;
retain historical baseline and measurements.
- No new runtime behavior in this PR.

## Included since 0.10.0
Merged changes cover intent-first instructions and consistent worktrees
(#113), consequence-based reviews and persistent follow-up context
(#114), consistent exhausted-budget guidance (#115), reduced mandatory
context and installed reference documents (#116).

## Verification
- Coordinator rerun `npm test`: 829 tests, 825 passed, 4 skipped, 0
failed.
- `npm run check`: exit 0, existing 14 warnings / 1 info.
- `npm run selfcheck`: OK; `git diff --check`: passed.
- Independent read-only release review: no material blockers; version,
manifest targets, runtime mirror and preserved measurement baseline
checked. Review conducted outside the STDD review runner.
- Implementer also exercised linux-x64 native workflow scenario, native
prebuild checks and npm package dry runs for CLI/plugin.
- Live model-backed contract harness not run; no publishing or consumer
installation performed.

Docs not applicable: release 0.11.0 version bump: generated stamps
regenerated per CONTRIBUTING Releases, no behavior change

## Upgrade and release boundary
After upgrading, consumers must re-run `stdd init` with their existing
tools/hook flags to receive `.stdd/reference/`. This PR does not update
any consumer project.

Merge this preparation PR before tagging. A separately authorized
`v0.11.0` tag on the merged commit triggers the repository release
workflow for npm packages and GitHub Release. No tag or publication has
been performed.
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.

1 participant