Jyotisha/docs/research/pre_work_error_ledger.md

Pre-Work Error Ledger

Purpose: read this file before substantial project work. It exists to stop repeat mistakes caused by multiple Codex windows, WorkBuddy mirrors, local drafts, backup folders, and partial cloud-git visibility.

Mandatory Pre-Work Check

Run or consciously verify:

sed -n '1,220p' AGENTS.md
sed -n '1,260p' docs/research/pre_work_error_ledger.md
git status --short --branch
git remote -v
python3 scripts/pre_work_check.py --remote-timeout 8 --command-timeout 45

The one-command gate must cover:

• tests/test_runtime_import_boundaries.py
• tests/test_project_fragment_governance.py
• tests/test_preflight_fragment_scan.py
• tests/test_remote_repo_visibility_check.py
• tests/test_pre_work_check.py

For large architecture or release work, also read:

• docs/research/whole_machine_fragment_sweep_round25_2026_06_25.md
• docs/research/whole_machine_fragment_sweep_2026_07_05.md
• docs/research/unique_main_chain_map_2026_07_01.md
• docs/research/local_drafts_2026_06_disposition.md

Error Ledger

ID	Error / Risk	Current Status	Required Guard
ERR-001	Runtime code pulled modules from .workbuddy distribution mirror.	resolved	Keep tests/test_runtime_import_boundaries.py; .workbuddy is reference only.
ERR-002	mcp_server.py documentation implied .workbuddy was a runtime path.	resolved	MCP top docs must point to main repo runtime; mirror wording must say distribution/reference only.
ERR-003	local_drafts mixed high-value research with disposable drafts.	mitigated	Use docs/research/local_drafts_2026_06_disposition.md; do not delete or promote drafts ad hoc.
ERR-004	Multiple local folders contain Jyotish fragments, older adapters, and WorkBuddy mirrors.	active	Read latest fragment sweep before changing adapters, oracle paths, or skill runtime boundaries.
ERR-005	Terminal git access to GitHub can fail even when the browser can open the repo.	active	Use python3 scripts/remote_repo_visibility_check.py; do not claim cloud sync unless status is verified.
ERR-006	Whole-machine find can time out when run too broadly.	active	Use split scans by directory and bounded -maxdepth; record timeouts as findings.
ERR-007	.workbuddy/skills/jyotish-vedic-astrology is a dirty historical mirror.	active	Never copy it over main repo. Use only for read-only comparison.
ERR-008	Current main workspace may be dirty with user/Codex changes.	active	Never reset or checkout. Read touched files before editing.
ERR-009	Astrology interpretation can drift into story-fitting from conversation history.	active	For blind technical reports, use only declared evidence packets/PDF and mark MEVG/real-case gaps.
ERR-010	VedAstro official/cloud evidence can be partial or dasha-conflicting.	active	Mark official closure partial unless exact endpoint/settings and raw output are verified.
ERR-011	Bare pytest command may be missing from PATH even when pytest module exists.	active	Use python3 -m pytest ... in acceptance commands.
ERR-012	Governance tests can fail if wording is narrower than the actual guardrail.	observed 2026-07-05	Keep tests tied to explicit user-facing terms such as 开工前 and the ledger path.
ERR-013	GitHub API can fail from terminal Python even when browser/Web can open GitHub.	active	Treat remote_repo_visibility_check.py status blocked as authoritative for terminal parity; browser visibility alone is not sync proof.
ERR-014	Pre-work checks can be skipped when split across several manual commands.	mitigated	Use python3 scripts/pre_work_check.py as the one-command pre-work gate.
ERR-015	One-command pre-work can exceed desktop outer timeout if child command timeout is too wide or scan runs twice.	observed 2026-07-05	Keep pytest child timeout bounded at 45s; let pre_work_check.py cache preflight_fragment_scan.py output for tests/test_preflight_fragment_scan.py.
ERR-016	Full tests/test_api_server_security.py can exceed the desktop outer timeout.	observed 2026-07-05	Use focused API test slices during development; reserve full API file run for longer verification windows.
ERR-017	Pre-work gate could pass without checking the older Round 25 fragment sweep or aggregate external-engine adapter diagnostics.	mitigated 2026-07-05	scripts/pre_work_check.py must require both whole-machine sweep docs and run scripts/diagnose_external_engine_adapters.py --json before substantial work.
ERR-018	External engine blockers can be described verbally but not carried into diagnostics.	mitigated 2026-07-05	diagnose_external_engine_adapters.py must expose VedAstro closure plan and PyJHora/JHora install/license/ephemeris boundary; keep docs/research/external_engine_blocker_research_2026_07_05.md current.
ERR-019	WorkBuddy/cloud/local acceptance summaries can invent pass counts, stale asset counts, non-existent error docs, or wrong dasha windows.	mitigated 2026-07-06	Read docs/research/user_invocation_acceptance_error_log_2026_07_06.md; run scripts/user_invocation_acceptance_check.py and tests/test_user_invocation_acceptance_contract.py before accepting ordinary-user skill invocation validation claims.
ERR-020	VedAstro official raw responses can be archived but hard to audit if no manifest/API listing exposes them.	mitigated 2026-07-08	Keep list_official_raw_response_archives() and GET /api/vedastro_gateway/archives; tests must prove archived official raw responses are enumerable.
ERR-021	VedAstro raw archive manifests can exist outside the high-rigor evidence packet, leaving final reports unable to prove whether official raw evidence was archived.	mitigated 2026-07-08	Keep vedastro_official_raw_archive_manifest in machine_evidence_packet.sections for API and MCP strict workflows.
ERR-022	Technique Audit Table can show VedAstro cloud state but omit whether archived official raw evidence is actually auditable.	mitigated 2026-07-08	Keep VedAstro Raw Archive Manifest as a first-class Technique Audit Table row immediately after VedAstro Cloud State.
ERR-023	professional_reading can require a Technique Audit Table while omitting the user-visible VedAstro raw archive row.	mitigated 2026-07-08	Keep VedAstro Raw Archive Manifest in professional_reading.technique_audit_table_required_rows.
ERR-024	VedAstro gateway status can choose local_fallback before .env is loaded, even when official endpoint/network settings are present.	mitigated 2026-07-08	gateway_status() must load official readiness before resolving active backend; run_gateway_packet() must expose official_closure_state separately from legacy status.
ERR-025	VedAstro gateway can report legacy status=ok from catalog availability even when no official raw response is present.	mitigated 2026-07-08	official_closure_state=official_verified requires official_raw_response; otherwise expose official_closure_reason=official_raw_response_missing.
ERR-026	VedAstro service adapter can obtain an official full-snapshot raw response while the user entrypoint drops it, leaving gateway official closure permanently blocked.	mitigated 2026-07-09	vedastro_user_entrypoint must expose vedastro_official_full_snapshot.raw_response_available and root official_raw_response when explicitly requested; gateway tests must prove raw propagation reaches official_verified.
ERR-027	External engine readiness diagnostics can be mistaken for a completed same-chart parity comparison.	mitigated 2026-07-09	diagnose_external_engine_adapters.py must expose same_chart_parity_contract.required_outputs, per-engine expected oracle fields, and tested=false until a real same-chart comparison runs.
ERR-028	Active birth-time rectification can stop at question generation and never narrow candidate clusters from user answers.	mitigated 2026-07-09	active_rectification_questions.score_answers() must turn A/B/C/D answers into cluster rankings, next-round questions, and an explicit boundary that final rectification still needs candidate chart differences.
ERR-029	Basic git and premium cloud-drive skill packages can blur contents, privacy exclusions, and external-engine promises.	mitigated 2026-07-09	scripts/skill_release_manifest.py must define edition contents, excluded private material, acceptance commands, and external-engine runtime boundaries before packaging.
ERR-030	Release packaging can misread non-ASCII tracked filenames when parsing quoted git ls-files output.	mitigated 2026-07-09	Package builders must use git ls-files -z and decode NUL-separated paths before writing zip archives.
ERR-031	Premium skill zip can ship without user install prompts or replay schemas, leaving users and future oracle imports without a contract.	mitigated 2026-07-09	skill_release_package.py must inject INSTALL.md and USER_PROMPTS.md; replay contracts must live in references/real_case_calibration/ and references/oracle/.
ERR-032	Full smoke files can time out while focused slices pass; test_full_reading_reports_ayanamsa_metadata_and_ai_prompt_pack currently exposes external_oracle_gap_summary=null.	observed 2026-07-10	Do not claim full tests/test_cli_smoke.py or full tests/test_vedastro_external_technique_evidence.py passed unless run to completion; use focused slices for related changes and track the prompt-pack gap separately.
ERR-033	Premium skill zip validation can accidentally depend on a parent Git repository, so a cloud-drive user may fail in a clean unzip directory.	mitigated 2026-07-10	Release acceptance must include tests/test_skill_release_clean_trial.py; scripts such as public_release_privacy_scan.py must support non-Git unpacked zip directories.
ERR-034	A single historical_event_backtest.build_report() strict replay can exceed 120 seconds before returning a case result.	observed 2026-07-11	Use scripts/public_real_case_benchmark.py for bounded batch evidence replay; keep strict workflow as a separately timed probe and report timeout as blocked.
ERR-035	benchmarks/jyotish/scripts/run_pyjhora_compare.py --help executes the benchmark and crashes when canonical fixtures are absent.	observed 2026-07-11	Do not claim PyJHora parity from readiness. Generate canonical fixtures or harden the runner before the next same-chart batch.
ERR-036	public_real_case_benchmark.py --rule-version compare originally replayed both rule versions and exceeded the 120-second command budget.	mitigated 2026-07-11	Compare mode must read precomputed --comparison-v1 and --comparison-v2 reports; never duplicate engine replay inside comparison.
ERR-037	scripts/muntha.py failed at import because List was used in an annotation but not imported.	resolved 2026-07-11	Keep tests/test_muntha_module.py; a technique file does not count as available unless it imports and runs independently.
ERR-038	Real-case scoring counted the same planet twice when MD and AD had the same lord, inflating strong-hit scores and duplicating signals.	mitigated 2026-07-11	V2.1 must deduplicate active lords before _planet_score; keep the same-MD/AD regression test and preserve legacy V2 reports for audit only.
ERR-039	exact_label_rate looked like classification accuracy even though the benchmark already knew the event domain and assigned the expected label at the strong threshold.	mitigated 2026-07-11	Use known_event_activation_rate and strong_activation_rate; keep old names deprecated and never present them as predictive accuracy.
ERR-040	.gitignore excluded only parts of scratch/, leaving local helper files and .serena/ visible to git add ..	resolved 2026-07-11	Ignore /scratch/ and /.serena/ at repo root; keep a regression test for both private workspace directories.
ERR-041	Positive-event replay scores were interpreted as timing evidence even though nearby non-target dates could receive equal or higher scores.	mitigated 2026-07-11	Keep the negative-control date-ranking pilot and timing_precision_gate; block exact-day/month claims while Top-3 ranking remains below the gate.
ERR-042	REST duplicated natal chart, Vimshottari and Sade Sati calculations, so True Node was ignored, the first Dasha balance drifted, and Saturn transit was fabricated.	resolved 2026-07-11	Keep tests/test_calculation_p0_regressions.py; domain/CLI/REST must share domain_calculation_service.py, effective parameters and result_hash.
ERR-043	Localhost POST requests trusted CORS response headers as an execution guard; report Chromium could load external/local resources; async job IDs were predictable and persisted without capability authentication or TTL.	mitigated 2026-07-11	Keep tests/test_runtime_security_p0.py; enforce Origin/Host/JSON, sandbox report resources, use random capability tokens, 0600 atomic records, TTL deletion and a bounded worker queue. Run an isolated Chromium network PoC before declaring the renderer fully hardened.
ERR-044	Focused selections that include legacy full chart API tests can still exceed the 120-second desktop command budget even after pure calculation tests pass.	observed 2026-07-11	Keep P0 calculation/security tests pure and fast; profile the legacy chart fixture separately before using the full API file as a blocking CI gate.
ERR-045	Three-engine readiness was mistaken for completed same-chart parity. Public replay on 2026-07-13 captured jyotishganit raw and found only a PyJHora dasha artifact; VedAstro still had no official raw response.	active external blocker	Keep three_engine_parity_runner.py; status remains blocked/partial until all required raw artifacts are normalized into comparison rows. Latest blocker: official_vedastro_raw_missing_or_unverified.
ERR-046	Report-renderer SSRF/file PoC was blocked until a Playwright Chromium binary was installed.	mitigated 2026-07-13	Keep route/JS-denial tests and run scripts/report_renderer_isolation_poc.py; only status=pass with zero HTTP probe requests and blocked file/http resources proves isolated rendering. Verified 2026-07-13: status=pass, http_probe_requests=0, blocked schemes file/http.
ERR-047	Initial slow marker partition for test_api_server_security.py still exceeded the 120-second desktop budget; heavy paths extend beyond VedAstro/high-rigor prefix groups.	active profiling blocker	Profile test node IDs in bounded subprocess batches, mark only measured heavy tests, and keep fast-security acceptance separate from long CI integration coverage.
ERR-048	Candidate-time scanner assumed all documented D4/D24/D30 divisions were exposed by jyotish_engine.py varga; actual --d4 failed at runtime.	mitigated 2026-07-12	Candidate scans must record unsupported Varga flags as unavailable_vargas; only successfully computed D1/D9/D10 fields may drive local sensitivity output until a unified Varga contract exists.
ERR-049	PyJHora benchmark runner executed on --help, used a wrong repository-root path in run_skill_baseline.py, and failed when reused without pre-created output directories.	mitigated 2026-07-12	Keep tests/test_pyjhora_compare_cli.py; require explicit --build-local, safe argparse help, correct repo root, and directory creation inside run_sample().
ERR-050	Prashna CLI/API/UI could synthesize or accept a non-question chart; legacy Tajika/Saham/Sphuta/Kunda paths also exposed approximate values as usable evidence.	mitigated 2026-07-14	Require backend Swiss PrashnaContext with question text/time/location/timezone; reject client planets/ascendant. The engine's deterministic fallback branch has been removed. Block legacy Sphuta/Kunda/Gulika/Panchavargiya and no-location Saham paths; keep seven-planet Tajika interactions partial until named-yoga golden cases and formula parity exist.
ERR-051	Privacy redaction can replace executable numeric test fixtures with bare placeholder identifiers such as REDACTED_YEAR, causing NameError before a regression reaches its target.	observed 2026-07-12	Public tests must use generic fixtures (for example 1990) or quoted placeholders only; run rg -n "REDACTED_YEAR" tests before release and repair executable occurrences.
ERR-052	Text-only privacy scanning cannot distinguish a harmless quoted placeholder from a bare Python identifier that will fail at runtime.	mitigated 2026-07-13	public_release_privacy_scan.py parses shipped Python files and rejects executable REDACTED_* names; keep the AST regression test.
ERR-053	A parity manifest could label an external engine official_verified without a raw artifact, hash, or calculation settings, making claimed oracle closure unverifiable.	mitigated 2026-07-13	three_engine_parity_replay_validator.py requires raw artifact existence, SHA-256 and settings for verified/imported external engines; otherwise parity is invalid.
ERR-054	Candidate-time sensitivity scanning used the legacy varga CLI, so D4/D24/D30 could appear unavailable despite being supported by varga-full.	resolved 2026-07-13	Scanner calls varga-full --divisions D4,D9,D10,D24,D30 once per candidate and reads its canonical Ascendant.sign fields.
ERR-055	The full-reading path called calc_all_sahams() without lat/lon/tz, so an otherwise computable Swiss day/night context was silently blocked.	resolved 2026-07-14	Pass the calculation arguments' lat/lon/tz into the Saham layer; keep Saham formula maturity partial until oracle parity exists.
ERR-056	A WorkBuddy checkout of the same remote diverged substantially from the active source branch and can be mistaken for a mergeable mirror.	active	Read whole_machine_fragment_sweep_2026_07_14.md; do not copy or merge it without explicit commit-level review on a separate branch.
ERR-057	The release quality profile checked untracked files but did not execute the privacy AST scan or the real Chromium report-isolation probe.	mitigated 2026-07-14	release_hygiene_check() now requires public_release_privacy_scan.py --json and report_renderer_isolation_poc.py --strict; parity manifest validation also runs as a contract check.
ERR-058	Formula-based Sahams used the day/night operand rules but omitted the documented zodiacal-order +30° exception.	mitigated 2026-07-14	_calc_formula_saham() applies the references/saham_rules.json forward-arc condition and one-sign correction; keep external numeric oracle parity as a separate partial requirement.
ERR-059	Gulika was either an approximate fallback or falsely implied as a chart module output.	mitigated 2026-07-14	scripts/gulika.py computes Prasna Marga Ghatika segment Ascendant with Swiss sunrise/sunset and Lahiri sidereal houses. It is exposed only as prashna_context.supporting_indicators.gulika, remains partial, and cannot unlock Sphuta or verdict layers until external numeric parity exists.
ERR-060	Legacy Sphuta functions combined approximate Gulika with interpretive signals, while the exact formula could not be inspected in the production question context.	mitigated 2026-07-14	prashna_sphuta.py exposes formula-only Trisphuta/Catusphuta/Pancasphuta from the partial Gulika evidence. It is supporting-only; Kunda, life-sensitive Sphutas and Prashna verdicts remain blocked pending external numeric parity.
ERR-061	Full-reading passed longitude-only data to the Tajika layer, permanently blocking its speed-dependent seven-planet interaction evidence.	mitigated 2026-07-14	Pass actual Swiss longitude/speed pairs. The output may expose only partial Ithasala/Easarapha candidates; named chains and event verdicts stay blocked pending golden cases.
ERR-062	A release gate could validate a parity manifest's shape without requiring all external engines to actually match, allowing “contract valid” to be mistaken for “oracle verified.”	mitigated 2026-07-14	three_engine_parity_replay_validator.py --require-pass fails unless parity status is pass; run_quality_gate.py --require-external-parity exposes this as an explicit high-standard release requirement.
ERR-063	High-rigor API output could omit the three-engine parity state, especially on plan-only responses, allowing downstream UI or MCP callers to overstate verification.	mitigated 2026-07-14	Every high-rigor execution and plan response carries high_rigor_external_parity; require_external_parity=true sets success=false unless parity is pass.
ERR-064	Western cross-system support accepted external JSON but did not calculate a tropical natal chart from standard birth input, inviting agents to treat missing Western data as a completed cross-check.	mitigated 2026-07-14	western_chart_engine.py computes Swiss Ephemeris tropical natal evidence for direct-chart/rectification only. It remains partial until separately materialized timing evidence exists; Prashna and external-payload precedence are regression-tested.
ERR-065	A newly added release-critical script can be absent from a zip before its first Git commit because the package enumerates tracked files only.	mitigated 2026-07-14	List scripts/western_chart_engine.py in REQUIRED_CONTRACTS; the release-package test proves both editions include it before commit.
ERR-066	The pre-work fragment sweep invoked a retired audit-capabilities --mode strict contract, so governance tests and the mandatory preflight failed before real checks ran.	mitigated 2026-07-14	Invoke the supported --mode validate; tests/test_preflight_fragment_scan.py and pre_work_check.py must remain green before substantive work.
ERR-067	A generic “Western timing” label can imply techniques that have not been computed.	mitigated 2026-07-15	Native timing requires explicit fields for each layer. Current native layers cover transit, solar-return, secondary-progression, solar-arc, converse, midpoint, lunar-return and daily duration scan; progressed angles, parans and interpretation remain explicitly blocked/partial.
ERR-068	PyJHora comparison reports hard-coded 2026-06-03 as generation time, making fresh external benchmark artifacts appear stale and weakening audit traceability.	mitigated 2026-07-15	write_report() records an injected-or-current UTC ISO timestamp; keep the deterministic timestamp regression.
ERR-069	Yoga validation tests and helper runner still imported rules from a .workbuddy mirror, so full pytest could fail or silently validate a divergent checkout.	mitigated 2026-07-15	Resolve repo root from each file location; retain runtime-boundary and focused Yoga regressions.
ERR-070	PyJHora parity for D2/D4/BAV/SAV can pass while Shadbala total virupas still mismatch, so a row-filled Shadbala oracle packet can be mistaken for absolute-value parity.	active external formula blocker	Keep docs/research/pyjhora_d2_d4_ashtakavarga_shadbala_parity_2026_07_15.md; do not claim Shadbala external absolute closure until component-level formulas reconcile with PyJHora/JHora raw values.
ERR-071	runtime-truth required an untracked scratch/local/pdf_review_123456 JHora packet, so a clean public checkout failed before it could report the actual external-oracle boundary.	resolved 2026-07-16	Release truth reads references/evidence_manifests/jhora_master_evidence_manifest.json; scratch is optional and may be repaired only through explicit sync_final_evidence_packet_status.py --sync-local. Manifest must retain external_raw_required_for_official_verified=true.

Fragment Sweep Command Set

Use split scans, not one unbounded full-home command:

for d in <home>/Documents <home>/WorkBuddy <home>/.workbuddy <home>/Downloads <home>/Desktop <home>/.codex/attachments; do
  [ -d "$d" ] && find "$d" -maxdepth 6 -type d -name .git 2>/dev/null | sed 's#/.git$##'
done | rg -i '印度|jyotish|vedic|astro|yinduzhanxing|workbuddy|星轨|codex|talk' | sort

for d in <home>/Documents <home>/WorkBuddy <home>/.workbuddy <home>/Downloads <home>/Desktop <home>/.codex/attachments; do
  [ -d "$d" ] && find "$d" -maxdepth 7 -type f \( -iname '*jyotish*' -o -iname '*vedic*' -o -iname '*jhora*' -o -iname '*shadbala*' -o -iname '*ashtakoot*' -o -iname '*印度占星*' -o -iname '*yinduzhanxing*' \) 2>/dev/null
done